Added Infra Node attributes UI and cypress test cases.

[chaitali-mane]

Signed-off-by: Chaitali Mane cmane@progress.com

🔩 Description: What code changed, and why?

• Add Edit/Update node attributes UI to update the node run list.
• Add cypress test case for the attributes, edit the attributes and change tab.
• Add Edit/Update node attributes UI on node list dropdown page.

⛓️ Related Resources

#4921

👍 Definition of Done

• Added UI for attributes tab.
• Added UI for edit attributes.
• Added dropdown for edit attributes on node list page.
• Added cypress test cases.

👟 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

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

Steps for attributes tab:

1. Go To Infrastructure -> Chef Servers -> click server name-> click on org name -> Nodes.
2. Click on particular node -> attributes tab -> will show list of attributes if particular node has it -> Edit button -> to edit the attributes and update.

Steps node dropdown for edit attributes:
1.Go To Infrastructure -> Chef Servers -> click server name-> click on org name -> Nodes.
2. Click on particular node -> click Edit attributes -> to edit the attributes and update.

For cypress Build
https://github.com/chef/automate/tree/master/e2e

✅ 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

1. UI for attributes tab
   

2. UI for edit attributes
   

3. dropdown for edit attributes
   

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 0a55a8e

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

[vinay033]

changes look good to me.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[himanshi-chhabra]

LGTM, Thanks @chaitali-mane

[chaitali-mane]

Found issue while acceptance testing. Created below issue #5255