Rename Visibility schema's version table to avoid conflict with Temporal schema

[Dox33]

Current Situation:

Temporal and Temporal Visibility schemas currently can't coexist in the same database because both utilize the same table name schema_version. This naming conflict causes versioning conflicts and blocks seamless schema upgrades.

Proposed Solution:

Rename the Visibility schema’s versioning table, e.g., from schema_version to something distinct such as visibility_version.

Benefits:

This would allow both schemas to coexist without conflicts, enabling smoother upgrades and coexistence of multiple schema versions.

Additional Context (Optional):

This suggestion arose from a discussion in https://community.temporal.io/t/allow-temporal-and-visibility-schemas-in-a-single-database-by-renaming-schema-version-table/17151.

Thank you!

[bergundy]

Related issue: #7658