Extend JSON permissions model to accommodate APIs that don't require permissions

Some APIs only require an Open ID connect scope but no Microsoft Graph permissions. We need a way to account for those HTTP requests in the permissions model so we can generate the right thing in the content. Extend the JSON model to include a place to track the request syntax for these APIs, and update the system to generate the alternative boilerplate text instead of the standard boilerplate and link/include file.

Boilerplate text: To call this API in application-only scenarios, your application must have a valid access token, but doesn’t require any Microsoft Graph permissions. In delegated scenarios, your app must be granted at least one delegated permission.

This issue applies to APIs with the following segment: /identityGovernance/permissionsAnalytics

Start by locating the JSON permissions model and the code that generates boilerplate and links or includes files. Use the /identityGovernance/permissionsAnalytics segment as the example, then verify that its request syntax is accepted and produces the alternative boilerplate text while existing permissioned APIs retain the standard output.