feat: Azure plugin - remove Palette presets, reading permission set files

[mattwelke]

Issue

Resolves #84
Resolves #45

Description

Changes the plugin to not have Palette presets for Azure RBAC rules anymore.

Also changes it to not prompt the user for details for permission sets anymore. Instead, that data is read from a file the user provides. Permission sets are the portion of the RBAC rule consisting of the actions, data actions, and scope. The principal is also part of the rule but the user is prompted for that instead of it being read from a file. Most plugin users won't need more than one rule because while they may have multiple levels of scope to work with, they will likely only be validating one principal. This should be very minimal prompting, with most data coming from the file.

Example:

Note: You must configure at least one rule for plugin configuration.
Note: Collecting input for rule #1
Rule type: 
  > RBAC
Rule name: rule-1
Enter security principal.
Format: Azure GUID
Example: d6df0bba-800d-492f-802e-d04a38c80786
Security principal: cc7f25f8-4ab7-4274-a684-1f5670cd6c60
Note: You must configure at least one permission set for rule.
If you're updating an existing RBAC rule, its permission sets will be replaced.
Permission sets file path: tests/integration/_validator/testcases/data/azurePermissionSets.json
Add additional RBAC rule? [y/N]: No

This is intentional:

Rule type: 
  > RBAC

validatorctl only supports RBAC rules right now, but more rules are being added to the plugin and they will be added to validatorctl later. Leaving this here as a placeholder.

[TylerGillson]

@mattwelke is this still WIP? Please update the description and rebase if it's ready for review.

[mattwelke]

@TylerGillson I'm going to refine this a bit. Instead of it prompting multiple times for permission set files until it has all the permission sets, I'm going to make a new JSON file format where users can specify all the permission sets at once. This would help in scenarios where they have more than one permission set because they require some permissions at scope x but other permissions only at scope y, and they don't want to over permission. And they'd be able to encode all of that in one file.

With the Azure plugin, while we can't make it so users can copy and paste JSON they find online (e.g. the JSON for a role they find on Azure' built-in roles page) until we have the new "role" rule we discussed offline, we can at least make it so that they have as few prompts to go through as possible because as much of the data as possible has been included in this JSON file.

[codecov]

Codecov Report

Attention: Patch coverage is 41.46341% with 24 lines in your changes missing coverage. Please review.

@@            Coverage Diff             @@
##             main      #97      +/-   ##
==========================================
- Coverage   52.28%   50.81%   -1.48%     
==========================================
  Files          45       45              
  Lines        5009     4719     -290     
==========================================
- Hits         2619     2398     -221     
+ Misses       1729     1695      -34     
+ Partials      661      626      -35     

Files	Coverage Δ
pkg/config/constants.go	100.00% <ø> (ø)
...integration/_validator/testcases/test_validator.go	94.43% <100.00%> (-0.48%)	⬇️
pkg/services/validator/azure.go	44.09% <38.46%> (-17.50%)	⬇️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b5326b...f7b3726. Read the comment docs.

[mattwelke]

Made that update. Rebased. Ready for review.

[mattwelke]

GitGuardian comment was about fake secrets in test package accidentally accidentally committed. Cleaned up branch.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}