migrate to msgraph

[chkeita]

This PR removes the references to soon to be deprecated azure-graphrbac and uses the Microsoft Graph Api instead
closes #870

Note this PR disables the undocumented feature of setting ONEFUZZ_AAD_GROUP_ID on the server

Test:

• run check-pr on on both windows and linux
• check that ONEFUZZ_AAD_GROUP_ID has been disabled
  • Add an application setting call ONEFUZZ_AAD_GROUP_ID to the instance azure function
  • Set the value to a guid
  • from the cli execute onefuzz jobs list
  • response: An error containing the error message "ONEFUZZ_AAD_GROUP_ID configuration not supported"

[chkeita]

Postponing the merge of this until linux machines are allowed to connect to Azure active directory.

[ranweiler]

I don't think our integration tests are sufficient to test this PR.

I think we really need to test the graph queries themselves, and in particular, make sure any code that uses them for membership tests rejects authorization as appropriate, based on group membership, in e.g. check_access().

[chkeita]

@ranweiler

I don't think our integration tests are sufficient to test this PR.

I think we really need to test the graph queries themselves, and in particular, make sure any code that uses them for membership tests rejects authorization as appropriate, based on group membership, in e.g. check_access().

The check_access was manually tested both by me and @nharper285 will update the description

[ranweiler]

Can we explicitly test (if we haven't already) and document (in the PR text) the new expected upgrade behavior if the $ONEFUZZ_AAD_GROUP_ID variable is set?

[chkeita]

ONEFUZZ_AAD_GROUP_ID behavior tested