[WIP] Add new component build model with per-version lifecycle management

[rcerven]

Implement new component model that manages build configurations and pipelines at the version level. Each version can be independently onboarded, triggered, and offboarded through component spec actions.

Key features:

• Per-version PaC configuration and pipeline management
• Action-based workflow (create configuration, trigger build, offboard)
• Version status tracking with error reporting
• Cache synchronization to prevent race conditions between reconciles
• Support for invalid version cleanup from actions

The new model is enabled via component annotation or default setting.

STONEBLD-4018

Checklist:

• PR has reference to the issue(s) it resolves
• Write / update unit tests
• Write / update integration (envtest) tests
• Ensure there is an issue for e2e tests if needed
• Ensure make test passes
• Ensure test coverage hasn't decreased
• Test code changes manually
• Update readme and documentation
• Write PR description that highlights overall changes and add usage examples if applicable

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.