fix: refresh pages automatically when a slice or subscriber is added/deleted/edited

[gatici]

Description

This is an UX improvement which refreshes the Subscriber and Network slices pages automatically when:

• A subscriber is added/deleted/edited
• A network slice is added/deleted/edited

For network Slices:

1. Uses the useMutation hook to handle adding, editing and deleting network slices.
2. Invalidates related queries to refresh the data from the server after the mutation succeeds.
3. Utilizes useState to manage the states updates.

For Subscribers:

1. Uses useMutation hook to handle the subscriber operations by invalidating the cache when the mutation completes successfully.
2. Utilizes useState to manage the states updates.
3. Uses window.location.reload to refresh the page when a subscribers is deleted.

Fixes: https://warthogs.atlassian.net/jira/software/c/projects/TELCO/boards/1079?assignee=61ad6623c510bc006b359f98&selectedIssue=TELCO-1477

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that validate the behaviour of the software.
• I validated that new and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

[patriciareinoso]

We have a task to remove the useEffect because is not the correct approach. Why are you adding it?

[gatici]

We have a task to remove the useEffect because is not the correct approach. Why are you adding it?

I think this task is about avoid using useEffect where it is not necessary. useEffect handles the interactions between components from inside or outside. If we do not use useEffect, the modules can not react to the changes comes from dependant components. I do not think it is possible remove all the useEffects in this repository.
For example:

    useEffect(() => {
        if (token) {
            let userObject = jwtDecode(token) as User
            userObject.authToken = token
            setUser(userObject);
        } else {
            setUser(null)
            router.push('/login');
        }
    }, [token, router]);

This code block is used in the authentication section which reacts on token and router changes and removing this approach produces undesirable consequences. I am exploring about it and it is out of this PR's scope.

[gatici]

We have a task to remove the useEffect because is not the correct approach. Why are you adding it?

The useEffect is removed from the PR. It's functionality is done by mutate handler functions for slice addition, edition and deletion.

[patriciareinoso]

I tested it and I still have the problem with the very first NS and subscriber created. If I delete them and recreate them, it works fine. The problem is the first one ever.
We can double check tomorrow

[gatici]

I tested it and I still have the problem with the very first NS and subscriber created. If I delete them and recreate them, it works fine. The problem is the first one ever. We can double check tomorrow

As you said I had it once in my first test attempt: I attached a custom image, then I saw that subscribers appears upon delete. Then, it did not appear again.

To simulate this behaviour, I reinstalled NMS charm several times and tested this feature using Firefox and Google Chrome. But it did not appear again. I really don't get the reason.

[patriciareinoso]

We double check and is working fine