Bump manifest jsonschema to v11, update v10 schema

[gshank]

resolves #8333

Problem

We need to bump the manifest schema version for main to v11. This also updates and freezes the v10 schema.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[codecov]

Codecov Report

Merging #8335 (b653c58) into main (556b404) will increase coverage by 0.02%.
Report is 3 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #8335      +/-   ##
==========================================
+ Coverage   86.23%   86.25%   +0.02%     
==========================================
  Files         174      174              
  Lines       25518    25518              
==========================================
+ Hits        22005    22011       +6     
+ Misses       3513     3507       -6     

Files Changed	Coverage Δ
core/dbt/contracts/graph/manifest.py	93.75% <100.00%> (ø)

... and 3 files with indirect coverage changes

[dbeatty10]

👍 LGTM

Additionally, what would be the trade-offs if we published these schema versions with pretty-printing applied?

On the benefit side of things, it would make it easier to see diffs whenever making changes to a core/dbt/contracts/graph/v{schema_version}.json file. But I'm not sure if it would have negative impacts, like performance, etc.

[gshank]

I personally almost always prefer pretty-printed json. I'm not sure what we post in the schemas repo... Will have to look. It does make the files bigger and our manifest schema is on the large size. There wouldn't be much of a performance impact because we don't use these file schemas in our code.

[FishtownBuildBot]

Opened a new issue in dbt-labs/docs.getdbt.com: dbt-labs/docs.getdbt.com#4205