Add authentication validation to the JSON schema

[sander1095]

Why make this change?

Closes #2643

The JSON schema does not contain a list of auth providers, nor does it validate the use of the jwt property. This results in a suboptimal developer experience. By adding this list and validation, developers have an easier time learning about all the options and can be more productive.

What is this change?

• This change modifies the JSON schema with a list of providers and validation of the providers and the jwt property. StackOverflow helped me with the finer details of the validation.
  • I also added tests to validate my changes.
• Migrate from NJsonSchema to Newtonsoft.Json.Schema because NJsonSchema doesn't validate anyof + const correctly. Newtonsoft.Json.Schema does work in this case.
• Changed https to http in the schema file to be spec compliant. Draft-07's original URL is http-based.
  • If you try to validate a document with the https url, it will fail because of the unknown schema URL.
  • This does not impact security. The schema should just be a placeholder for the json validator binary to know what rules to use, and it's redirected to https when you navigate to it, anyway.

How was this tested?

• Integration Tests
• Unit Tests

Sample Request(s)

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Aniruddh25]

LGTM! Thanks for adding this validation and improving developer experience.

[sander1095]

@Aniruddh25 I've processed your comments.

I took a look at the failures of the CI pipeline of the last commits. They seem to be unrelated to my changes: The task has failed because you are using Ubuntu 24.04 or later without mono installed. See https://aka.ms/nuget-task-mono for more information..

Let's hope that a re-run will make them go green!

[sander1095]

@RubenCerna2079 Could you perform a re-run on this PR :)

[Aniruddh25]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[sander1095]

I see I broke some config tests. I'll hopefully have time to look into this next week!

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Aniruddh25]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Aniruddh25]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[sander1095]

I can now see the integration test failure reasons! Some of them fail because the package migration changed the JSON Schema result messages. I can update this soon.

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Aniruddh25]

LGTM, thanks for pushing through this.

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[RubenCerna2079]

Hey @sander1095, I saw that the tests that were failing are not due to your PR, so I decided to ignore them in order to get your PR in. I will solve this issue in a separate PR. Thanks for your work!

[RubenCerna2079]

LGTM! Thank you for these changes!

[Aniruddh25]

Thank you for these contributions!