Validate frontend API and enum contracts

[izkgao]

Description

Closes #157, #162, and #177.

Blocked by companion frontend PR: CARTAvis/carta-frontend#2922 (merged)

This PR aligns carta-python with the CARTA frontend's renamed boolean and validation properties and adds machine-checkable API and enum contracts for development-time compatibility checks.

What is implemented:

• Update wrapper property paths and region handling to match the current frontend contract, including validation for unsupported annulus operations.
• Add source-aware enum registries plus API and enum manifest extractors, with unit coverage for extraction, aliases, and duplicate registrations.
• Document the API contract workflow and add a dev CI job that checks generated carta-python manifests against carta-frontend.

Checklist

For linked issues (if any):

• assignee and labels added
• GitHub Project estimate added

For the pull request:

• reviewers and assignee added
• GitHub Project estimate added
• tests added or updated / no tests needed
• documentation updated / no documentation update needed

For dependencies and compatibility:

• companion frontend or backend PRs linked / no companion PRs needed
• pyproject.toml and uv.lock updated / no dependency changes
• CARTA compatibility table updated when the minimum CARTA series changes
  or dev starts a new carta-python major/minor series / no compatibility
  change

For pull requests targeting main:

• VERSION.txt finalized for the release
• final compatibility entry matches the release major/minor version and
  minimum supported CARTA series

[confluence]

I'm going to wait until the other PRs have been resolved before doing a final review, but I have an alternative suggestion for specifying the links to protobuf and frontend enums:

• Create mix-in classes called FrontendEnum and ProtobufEnum.
• For each of these, implement a registration mechanism for subclasses (similar to the region and view mechanism), which:
  • Checks the subclass for an optional snapshot_name class attribute (maybe this should be called something like external_name or reference_name -- and it should probably be in all caps for style consistency)
  • Updates a class dict that maps snapshot names to enum subclasses (if no custom snapshot_name is provided, the name of the class is used by default)
• Make each class that is linked to a frontend or protobuf enum inherit one of these mixins.

Now by default enums won't be linked to anything, and you can access the mappings of the mixins to get the lists of frontend- and protobuf-linked enums (instead of having to tag every enum and parse them all manually), and you don't have to provide external names explicitly unless the class name is different.

[izkgao]

I removed the unrelated code changes from zhenkai/check_version branch so it can be reviewed independently.

[izkgao]

I found that it would be better to make it work without launching CARTA. I will make a script in frontend to generate a list of enum and use it for validation.