Sync API permissions in JSON file with Markdown documentation

[james-garriss]

💡 Summary

Microsoft recently created an API permissions file in JSON that lists and consolidates all of the permissions that ScubaGear needs to access the various M365 APIs. We need to ensure that these permissions are sync'd with those listed in our documentation:

https://github.com/cisagov/ScubaGear/blob/main/docs/prerequisites/interactive.md
https://github.com/cisagov/ScubaGear/blob/main/docs/prerequisites/noninteractive.md

Motivation and context

This should ensure that our documentation is in sync with reality.

Implementation notes

There are at least 3 ways this could be done:

• The docs could just point to JSON, which is what our dependencies page does. This is perhaps the best way to avoid DRY.
• There could be a utility or a workflow that that reads the JSON and creates corresponding Markdown. Microsoft has indicated that they already have code that could do this (or be mod'd to do this).
• There could be a utility or a workflow that reads the JSON and the Markdown files and compares the two of them.

Acceptance criteria

How do we know when this work is done?

• There is a non-manual way to verify that the required permissions are sync'd with the docs.