Infra node reset client key

[vinay033]

Signed-off-by: Vinay Sharma [email protected]

🔩 Description: What code changed, and why?

we need to allow users to reset the Key for a Node.

⛓️ Related Resources

#4917

👍 Definition of Done

I have covered the below mentioned points

• I have added the feature to reset the node key
• I have added the cypress specs for this feature

👟 How to Build and Test the Change

STEP 1
inside the hab studio

[default:/src:0]# build components/automate-ui-devproxy/
[default:/src:0]# start_automate_ui_background
[default:/src:0]# start_all_services

STEP 2
open new window
go to automate UI path

$ cd components/automate-ui
and run the command 

npm run serve:hab

navigate to `https://a2-dev.test/infrastructure/chef-servers`
add some sample data and then test the changes using tab change

To add data https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views

Go to the -->  `infrastructure tab` from the top navigation bar then you can see the `Chef Infra Server`
If you have data then you can see the list of servers 
--> then click to any of the servers --> see the list of org's
--> click to any of org ---> you can see the multiple tabs --> default tab is cookbooks tab 
--> you can see the nodes tab ---> click to nodes tab
--> if nodes are available then you can see the list of nodes with search and pagination.
--> you can see the `...` three-dot on the right side for each node when you click you can see the reset key option.

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

reset-node-key.mp4

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 3c71286

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/60ae15308c5cbf0008aa87d9

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[SEAjamieD]

Great work @vinay033! 🎉

[himanshi-chhabra]

Changes look good Thanks @vinay033