Enhance all Companion Product Database Managers to produce upgrade scripts without connecting to database

Feature Request: Offline Companion Product Database Upgrade Script Generation

Summary:
Enable companion product database managers to generate version-appropriate upgrade scripts without requiring a live database connection. This allows teams to produce, review, and automate deployment of upgrade scripts as part of environment provisioning and CI/CD workflows.

Problem Statement:
Currently, upgrading a companion product database requires connecting directly to a live database to verify its version and generate the appropriate upgrade steps. This makes it difficult to support automated environment creation and repeatable deployments, since upgrade logic is tightly coupled to an existing database instance. It also introduces friction for teams who want to prepare upgrade packages in advance or manage upgrades in environments that are not yet provisioned or are restricted from direct connections.

Proposed Solution:
Allow each Companion Product Database Manager to:

• Accept an input “from version” and “to version” (or infer valid upgrade paths from supplied metadata) without querying a live database.

• Generate a deterministic set of SQL (or equivalent) upgrade scripts based solely on product version metadata and schema evolution rules.

• Support both single-step (e.g., v1.5 → v1.6) and multi-step upgrades (e.g., v1.2 → v1.6 via 1.3, 1.4, 1.5) by composing the appropriate script chain.

• Output scripts in a format suitable for automation pipelines (e.g., as files/artifacts that can be consumed by deployment tools).

• Optionally validate the requested upgrade path and fail fast with clear errors if the path is unsupported or requires manual intervention.

• Provide a CLI and/or API interface so that upgrade script generation can be integrated into environment build pipelines (e.g., infrastructure-as-code or CI/CD jobs) without requiring UI interaction.

Benefits:

• Enables automated build-out of companion product environments without manual database interaction.

• Reduces deployment time and human error by treating upgrade scripts as predictable, pre-generated artifacts.

• Improves support for CI/CD and infrastructure-as-code patterns by decoupling script generation from live database access.

• Simplifies planning and compliance reviews by allowing teams to review upgrade scripts before they are executed in any environment.

• Increases operational consistency across environments (dev, test, staging, production) by using the same generated scripts everywhere.