[project tracking] v2 Schema work to do

[jsuereth]

Baseline integration

• Create V2 schema for defining models.
• V2 Schema for registry resolve (V2 Resolved Schema #980)
• V2 Schema for registry generate (@jsuereth)
  • V2 Schema in Jinja Templates (V2 Resolved Schema #980)
  • V2 Schema in rego policies (Update code so weaver check now supports v2 schema. #1016)
  • V2 Helper functions for jq/jinja (Add v2 support to JQ helpers  #1058)
• V2 Schema for registry check
• V2 Schema for registry update-markdown (Update-Markdown now supports v2 #1064)
• V2 Schema for live-check (@jerbly) (Schema v2 live-check #1022)
• V2 Schema for json_schema (Update registry json-schema to support V2 schema. #1047)
• V2 Schema for emit (@jerbly) (v2 emit #1019)
• V2 Schema for registry search (Or deprecate?) (@jerbly) (Deprecate search #1057)
• V2 Schema for diff (Implement weaver registry diff on V2 schema #1053)
• V2 Schema for registry stats
  • Stats for signals (Implement half of weaver registry stats for V2. #1037)
  • Stats for refinements
• Documentation (@lmolkova)

Features

• Fix attribute tracking so only "attribute definitions" wind up in attribute registry.
• [v2 schema] Decide what public Attribute Groups are and how they work in the weaver model. #989
• Decide on Namespacing / what belongs in manifest
• Lineage tracking for V2
• Code cleanup for overall "running weaver".
• The input to policies can be different between v1, v2: Document exact datamodel for values sent to REGO policies #694