Migrating use case types from previous releases

During an upgrade, the application automatically migrates existing use case types to the version-enabled model while preserving existing configurations and associations.

1. The application assigns version 1.0.0 to each existing use case type.
2. The migrated version is set as the Active version.
3. The version retains existing configuration data, including filters, categories, subcategories, document entities, and table schemas.
4. Existing namespace associations continue to function without changes.
5. The migration process is idempotent and can be executed multiple times without affecting existing data.