Allow Temporal and Visibility Schemas in a Single Database by Renaming schema_version Table

Currently, Temporal and Temporal Visibility schemas can’t coexist in one database because both use the same schema_version table, causing version conflicts and blocking seamless upgrades.
Would it be possible renaming the Visibility schema’s table (e.g., to visibility_version) to resolve this and enable smooth schema updates to newer versions?