test(client): multiSchema, test same table name

[Jolg42]

Closes #15009

We previously tested different table names because of a bug in validation, this PR changes that to test the same table name but in 2 different db schemas.

[danstarns]

Looks good to me, I assume we are waiting on an engine's version for this to pass. Happy to merge once its green.

[Jolg42]

Waiting for #15649 for engines

[Jolg42]

Currently fails with
https://github.com/prisma/prisma/actions/runs/3189841431/jobs/5204140972#step:10:2842

FAIL tests/functional/multi-schema/tests.ts (14.334 s)
  ● multi-schema (provider=postgresql, mapTable=true) › create

    Schema validation error - Error (query-engine-node-api library)
    Error code: P1012
    error: Error parsing attribute "@id": The given constraint name `some_table_pkey` has to be unique in the following namespace: global for primary key, indexes and unique constraints. Please provide a different name using the `map` argument.
      -->  schema.prisma:14
       | 
    13 |     model User {
    14 |       id String @id @default(cuid())
       | 
    error: Error parsing attribute "@id": The given constraint name `some_table_pkey` has to be unique in the following namespace: global for primary key, indexes and unique constraints. Please provide a different name using the `map` argument.
      -->  schema.prisma:23
       | 
    22 |     model Post {
    23 |       id String @id @default(cuid())
       | 

    Validation Error Count: 2
    [Context: getDmmf]

[Jolg42]

New engines from prisma/prisma-engines#3269 are now showing a different error.

https://github.com/prisma/prisma/actions/runs/3228011532/jobs/5283599499#step:10:4693

       db error: ERROR: relation "some_table" already exists
      0: sql_migration_connector::apply_migration::migration_step
                 with step=CreateTable { table_id: TableId(1) }
                   at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:21
      1: sql_migration_connector::apply_migration::apply_migration
                   at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:10
      2: migration_core::state::SchemaPush
                   at migration-engine/core/src/state.rs:380
      Error: db error: ERROR: relation "some_table" already exists
      0: sql_migration_connector::apply_migration::migration_step
                 with step=CreateTable { table_id: TableId(1) }
                   at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:21
      1: sql_migration_connector::apply_migration::apply_migration
                   at migration-engine/connectors/sql-migration-connector/src/apply_migration.rs:10
      2: migration_core::state::SchemaPush
                   at migration-engine/core/src/state.rs:380

@tomhoule it seems something is missing for SchemaPush

[Jolg42]

The error is expected because multi schema migrations are not yet implemented

[Jolg42]

Since Migrate support is needed to do this test in the functional test suite, I did it in the old integration tests #15798