Add databricks labs ucx migrate-tables and a related workflow

[nfx]

databricks labs ucx migrate-tables to apply table mapping from CSV file with the following columns: src_workspace_name,dst_catalog,src_schema,dst_schema,src_table,dst_table . Consider the following stages:

Initial assessment
We scan all tables, generate an inventory, get all perms, etc.
We provide a mapping file the customer can customize, but seed the UC table name with something like the workspace name or ID as the catalog.
Customer can choose to modify the mapping or not

Initial migration
We use the mapping file to sync tables, apply perms, and persist the mapping data in inventory

Repeated migration - this is probably a job that runs on schedule and the user should be instructed to configure accordingly
We use the mapping data in inventory to re-sync any tables, but not re-apply permissions as these probably changed.

Fine-grained:

• [EPIC] Migrate EXTERNAL tables from cloud storage accounts #333

Upstream dependencies:

• Automatically assign a UC Metastore to a workspace #341
• [FEATURE]: Create UC External Location, Schema, and Table Grants based on workspace-wide Azure SPN mount points #94
• Create EXTERNAL LOCATIONs to map to External Tables (Azure) #100
• Add databricks labs ucx table-mapping command #669

Next quarter:

• Allow skipping DBFS Root Delta Table if size exceeds preconfigured threshold #334
• [FEATURE]: Connect _migrate_table_create_ctas to migrate-tables workflow #332
• Migration corner-case: what if the schema changed upstream in Hive. SYNC is supposed to be idempotent and intended to run multiple times. #319
• Add databricks labs ucx validate-table-locations command #673

[FastLee]

1. We have to make sure that the mapping is validated and no conflicts were found prior to migration.
2. Make sure the external locations required for the migration were created and that the user has created table permissions on these external locations.