Disable apply button at initial state and move agents to their original position

[sortiz1191]

Hi team!

When managing agents into a group generates an error, all the agents move to their original positions.
Also, the Apply changes button is disabled when all the agents are in their original position.

To test it:

1. Go to Management/Groups

• Given the browser is in wazuh app with more than 1 user available
• When the user navigates to Management/Groups
• Then the Groups section will be shown

2. Create a Group

• Given the Group section
• When the user click in add new group
• And the user fill the name with "test"
• And the user click on "Save new Group"
• Then the group will be displayed in Groups table

3. Enter in Manage Agents in Groups section

• Given the group section with the group "test" created
• When the user click on test
• And the user click on "Manage agents" in the Test group section
• Then the agents will be displayed in Available agents and current agents in the group will be empty

4. Try to move agents in Manage agents of group test

• Given the section to move agent from some groups
• When the user can move all agents to the right or left back, save them and move them again
• Then the button to save will be enabled if the user move some of the users and there isn't any errors (except when the user will try to move an inactive or never connected agent, that will persist in the left side)

Solves: #3332

[asteriscos]

Test: ❌

When one of the agents is added and the rest is not, it doesn't end in the right group column. Also, the See full error doesn't do anything. In addition, the number of added or removed items is not reset after the operation.

[mpRegalado]

The code performs the function required. Upon encountering an error, it reverts all the changes to its original state.
However, the way that it does so causes further errors to be logged into the console.

Examining the code in wzRequest, it rejects the promise if the response contains failed_ids, never updating the failedIds array and causing the code to attempt and remove agents that do not belong in the group, causing the error.

[mpRegalado]

This functions mutates the state. It doesn't seem to have been changed in this PR but it should be addressed in another issue

[asteriscos]

Test: ❌
There's an odd behavior when adding multiple agents and some of them throw an error after saving the changes.
The agents that were successfully added are not shown in the group and the changes can be seen after reloading the page or switching views.

The expected result would be to show the successfully added agents in the right column and the ones that failed on the left.

[mpRegalado]

Error in console persists

[CPAlejandro]

I have just seen this bug, when you put the agent in a group, you move it back, saving all times and then try to enter the group another time, the button is disabled.

[asteriscos]

Test: ❌

There seems to be an issue with the state of added and removed agents.
After adding or removing one agent, its state cannot be changed again.

[asteriscos]

Test: ✔️
CR: ✔️
Possible minor improvements

[asteriscos]

Possible small Improvement: You could map classNames with the item.type so the className prop of the option is easier to read.
like className={ typeClasses[item.type] }

[asteriscos]

Possible small Improvement: You could map classNames with the item.type so the className prop of the option is easier to read.
like className={ typeClasses[item.type] }

[CPAlejandro]

CR and Testing: LGTM!