feat: add initial extension support

[wackywendell]

Summary

Begins addressing #367 and #342 by adding support for parsing the types in YAML Simple Extension Files into Rustic types - with validity enforced. This includes a string text parser handling built-in types, compound types, named structs, custom types, and validated parameter constraints in the Simple Extension YAML files.

Scope

• Types-only: no functions or call validation yet.
• Public API exposes parsed types (ExtensionFile, Registry, CustomType, ConcreteType) and enforces validation of those on creation / read.

Key Changes

• Type system
  • New BuiltinType, CompoundType, ConcreteType, CustomType with Display/round‑trip support for alias and named‑struct structures.
  • Parameter constraints: data type, integer (with min/max), enum (validated/deduped), boolean, string.
  • Parsing to and from the YAML structures (TryFrom<TypeParamDefsItem>, Parse<RawType>)
• File/Registry type: abstraction for handling YAML files
• Context and proto glue
  • Separates out ProtoContext from Context, to distinguish between things needed for Protobuf parsing (ProtoContext)
• Type expression parser
  • Parses simple, user‑defined (u!Name) and type variables; visits extension references for linkage bookkeeping.
• Build/CI
  • parse feature includes serde_yaml; include!(extensions.in) is gated behind extensions feature.
  • Aligns actions/checkout to v4, updates Cargo dependency set, and bumps the substrait submodule.

Compatibility Notes

• New trait bound ProtoContext on proto parsing that previously required only Context.
• extensions.in now compiled only with features=["extensions"].
• Minimal, types-only round‑trip implemented; other sections remain empty when converting back to text.

Testing

• New unit tests cover:
  • Type parsing and round‑trip for alias and named‑struct.
  • Parameter constraint handling including enum validation and integer bounds (with current truncation behavior).
  • Registry creation and type lookup; core registry smoke test behind features=["extensions"].

[benbellick]

Left a few comments but still haven't gone through most of the PR. Just wanted to flush what I have so far, but I will review more later. Thanks!

[benbellick]

Just to clarify, it looks like regress was already present before. Is this comment just clarifying why it was there in the first place?

[benbellick]

Can we just consistently use URN here? We have support for both in all of the other libraries and we will be dropping URI eventually.

[benbellick]

As mentioned, I don't have a ton of Rust experience, so it may be that this is totally standard.

But I wonder if there's a simpler way to handle parsing that isn't so trait-heavy. AFAICT, there is only one implementor of the ProtoContext trait, which is the test fixture (lines 81-107).

Could we drop the ProtoContext trait and use a concrete type instead, then update tests to use explicit instantiations of that type? If not, what is the benefit of using this trait here?