Shorthand bypass flag (required to implement JTD and other schema formats support)

[josh-hemphill]

Prerequisite for further JTD Schema integration

It allows users that need it, to manually substitute a JTD instance of AJV into instances of Fastify, or create a ValidatorCompiler that parses anything other than JSON Schema, by preventing Fastify from mutating schemas internally if they don't match JSON Schema root properties.

The result of the work on #3096 but PRed against main.
Related #3083

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[zekth]

Minor comment for documentation format consistency.

[josh-hemphill]

I removed the JTD tests at Eomm's suggestion, since they were only loosely coupled, relying on external dependencies, and I now believe don't make sense in this specific PR, as I mentioned in the comments.

I wanted to have a test that implemented JTD, but now I'm thinking it is indeed a bit misplaced since this PR isn't specifically adding JTD support anyway, testing one of many possible use cases probably isn't the right test to have there.

[zekth]

lgtm

[mcollina]

@Eomm could you please take a final look before landing?

[mcollina]

lgtm

[Eomm]

I removed the JTD tests at Eomm's suggestion, since they were only loosely coupled, relying on external dependencies, and I now believe don't make sense in this specific PR, as I mentioned in the comments.

thanks @josh-hemphill

The commit history will be helpful for the jtd anyway 👍🏽
We have explored that this is doable in this way

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.