adding root permissions for CS-erchef pkgs.

[talktovikas]

:nut_and_bolt: Description: What code changed, and why?

While testing the license enforcement at embedded chef-server, We are suppose to provide these permissions to the erchef.

:chains: Related Resources

:+1: Definition of Done

:athletic_shoe: How to Build and Test the Change

:white_check_mark: 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.

:camera: Screenshots, if applicable

[netlify[bot]]

👷 Deploy Preview for chef-automate processing.

Name	Link
🔨 Latest commit	7e8a7e7d7db336bebf8556005f5191f857a61f83
🔍 Latest deploy log	https://app.netlify.com/sites/chef-automate/deploys/67124055de4a7f00082db5fa

[sonarqube-for-infrastructure-prod[bot]]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube