Change the endpoint to get Wazuh manager auth configuration

[asteriscos]

Description

This pull request aims to use a manager or cluster endpoint to get the authentication configuration of the Wazuh server. Previously it used the agent endpoint filtered by the manager ID 000, which may cause RBAC issues.

It also fixes the order of the RBAC options in the create/edit policies view, so they appear in alphabetical order.

Issues Resolved

Closes #6203

Evidence

GET auth request

Ascending order of the RBAC options

Test

• Check the manager auth configuration request uses either the manager or cluster endpoint:
  https://documentation.wazuh.com/current/user-manual/api/reference.html#operation/api.controllers.cluster_controller.get_node_config

• Configure a password in the manager and check the register agent wizard sets the password properly in the script:
  

• Check the actions SuperSelect options are in alphabetical order:
  

Check List

• All tests pass
  • yarn test:jest
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

Code coverage (Jest)	%	values
Statements	11.73%	( 4048 / 34502 )
Branches	7.96%	( 1855 / 23297 )
Functions	11.26%	( 930 / 8256 )
Lines	11.91%	( 3937 / 33042 )

[lucianogorza]

CR ✅

Test ✅

GET auth request

Configure a password in the manager and check the register agent wizard sets the password properly in the script

Check the actions SuperSelect options are in alphabetical order

LGTM

[Tostti]

Test

• Check the manager auth configuration request uses either the manager or cluster endpoint:
  
  

• Configure a password in the manager and check the register agent wizard sets the password properly in the script:
  

• Check the actions SuperSelect options are in alphabetical order:
  

Test ✅
CR ✅

LGTM