Migration from Eclipse link to Relational JDBC as a metastore

### Describe the bug

Hey Team,

We are using older version of Polaris repo with eclipse link as metastore and that is currently deployed in our production environment.
I see the major breaking changes in DB schema with both the metastores with postgres as backend.

Eclipse link as metastore after being bootstrapped creates following tables in the DB

When I am bootstrapping with Relational JDBC with latest incubating polaris repo, the DB schema looks like this

I see following changes in the DB schema

- Dropped tables: entities_active, entities_change_tracking, polaris_sequence, sequence
- Renamed principal_secrets → principal_authentication_data
- Added new table: polaris_mapping_records
- Added realm_id column to existing tables
- Change default schema from public to polaris_schema

We would like to upgrade the Polaris to this latest with relational JDBC as we are facing issues with eclipse link as metastore. Was this change made ensuring the backward compatibility?

Start by reviewing the reported bootstrap schema differences between EclipseLink and Relational JDBC, especially the dropped, renamed, and added tables, realm_id, and the default schema change. Compare the migration and metastore bootstrap behavior for PostgreSQL and determine whether an upgrade path is defined. Done means the backward-compatibility behavior and any required migration path are documented or addressed.

Written by the indexing model from the issue text.