[Migration] Support same client Id for applications over different tenants

[ThaminduDilshan]

Describe the issue:
Currently in IS client ID is considered to be unique across the server and as a result the same client ID cannot be used in two different tenants. This capability is provided with #16370 improvement. A migration client should be provided to migrate older users to the new version.

Related issue

• Support same client Id for applications over different tenants #16370

[ThaminduDilshan]

Details and steps should be added to the migration docs.

1. Prerequisites on configs (tenant qualified urls and tenanted sessions)
2. DB constraint update
3. Schema migrator configs

    -
   version: "7.0.0"
   migratorConfigs:
    -
      name: "ClientIdTenantUnificationMigrator"
      order: 1
      parameters:
        location: "step2"
        schema: "identity"
   

4. Prerequisite for tenanted console/ myaccount and legacy behavior config

[ThaminduDilshan]

We need to do this once the migration docs are added

[isharak]

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!