refactor(v2_migrations): re-organize v2 migrations

[SanchithHegde]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR reorganizes the v2 related database migrations into the following 4 groups, instead of the previous migrations which were organized based on tables affected:

1. Migrations that only add new columns: These migrations can/should be run fearlessly, since they only introduce new columns and thus should not affect the working of the v1 application.

2. Migrations to re-create ID columns for v2: These migrations only involve dropping the SERIAL id columns from the v1 application in favor of the VARCHAR(64) id columns for the v2 application.

3. Migrations that update database constraints: These migrations are concerned with updating the primary key constraints, and updating unique constraints and indexes as required by the v2 application.

4. Migrations that drop columns from v1: These migrations drop columns from the v1 application that are no longer read by the v2 application. These should not be run on any of our hosted environments, until the v1 application is no longer in use.

   ❗ Running these migrations on hosted environments will cause loss of data!

In addition, this PR addresses some clippy lints thrown from v2 code.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

This PR re-organizes the existing v2 related database migrations.

Motivation and Context

This should make it easier for us to run the queries which do not affect the functioning of the v1 application and avoid running the destructive ones with higher confidence.

How did you test it?

Sanity testing with Postman.

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with SemanticDiff.

Analyzed 12 of 46 files.

Overall, the semantic diff is 27% smaller than the GitHub diff.

File Information

	Filename	Status
❔	v2_migrations/2024-08-28-081847_drop_v1_columns/down.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081847_drop_v1_columns/up.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081838_update_v2_primary_key_constraints/down.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081838_update_v2_primary_key_constraints/up.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081747_recreate_ids_for_v2/down.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081747_recreate_ids_for_v2/up.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081721_add_v2_columns/down.sql	Unsupported file format
❔	v2_migrations/2024-08-28-081721_add_v2_columns/up.sql	Unsupported file format
❔	v2_migrations/2024-08-12-075913_make_profile_id_mandatory_in_mca/down.sql	Unsupported file format
❔	v2_migrations/2024-08-12-075913_make_profile_id_mandatory_in_mca/up.sql	Unsupported file format
❔	v2_migrations/2024-07-31-100300_business_profile_add_v2_columns_drop_v1_columns/down.sql	Unsupported file format
❔	v2_migrations/2024-07-31-100300_business_profile_add_v2_columns_drop_v1_columns/up.sql	Unsupported file format
❔	v2_migrations/2024-07-31-065721_mca_v2/down.sql	Unsupported file format
❔	v2_migrations/2024-07-31-065721_mca_v2/up.sql	Unsupported file format
❔	v2_migrations/2024-07-30-100323_customer_v2/down.sql	Unsupported file format
❔	v2_migrations/2024-07-30-100323_customer_v2/up.sql	Unsupported file format
❔	v2_migrations/2024-07-29-063217_drop-org_id-and-org_name-from-organization/down.sql	Unsupported file format
❔	v2_migrations/2024-07-29-063217_drop-org_id-and-org_name-from-organization/up.sql	Unsupported file format
❔	v2_migrations/2024-07-26-065428_remove_deprecated_field_from_merchant_account/down.sql	Unsupported file format
❔	v2_migrations/2024-07-26-065428_remove_deprecated_field_from_merchant_account/up.sql	Unsupported file format
❔	v2_migrations/2024-07-25-065542_drop_merchant_id_from_merchant_account/down.sql	Unsupported file format
❔	v2_migrations/2024-07-25-065542_drop_merchant_id_from_merchant_account/up.sql	Unsupported file format
❔	v2_migrations/2024-07-25-065100_change_primary_key_from_merchant_id_to_id/down.sql	Unsupported file format
❔	v2_migrations/2024-07-25-065100_change_primary_key_from_merchant_id_to_id/up.sql	Unsupported file format
❔	v2_migrations/2024-07-25-064644_add_id_in_merchant_account/down.sql	Unsupported file format
❔	v2_migrations/2024-07-25-064644_add_id_in_merchant_account/up.sql	Unsupported file format
❔	v2_migrations/2024-07-19-073520_remove_id_from_merchant_account/down.sql	Unsupported file format
❔	v2_migrations/2024-07-19-073520_remove_id_from_merchant_account/up.sql	Unsupported file format
❔	v2_migrations/2024-06-03-133421_remove_id_from_payment_table/down.sql	Unsupported file format
❔	v2_migrations/2024-06-03-133421_remove_id_from_payment_table/up.sql	Unsupported file format
❔	migrations/2024-08-29-135449_add_version_to_business_profile/down.sql	Unsupported file format
❔	migrations/2024-08-29-135449_add_version_to_business_profile/up.sql	Unsupported file format
❔	migrations/2024-08-29-135449_add_api_version_to_business_profile/down.sql	Unsupported file format
❔	migrations/2024-08-29-135449_add_api_version_to_business_profile/up.sql	Unsupported file format
✔️	crates/router/src/core/admin.rs	Analyzed
✔️	crates/router/src/core/payment_methods.rs	6.25% smaller
✔️	crates/router/src/core/payouts.rs	0.0% smaller
✔️	crates/router/src/core/payments/helpers.rs	88.97% smaller
✔️	crates/router/src/core/payments/tokenization.rs	Analyzed
✔️	crates/router/src/core/payment_methods/cards.rs	Analyzed
✔️	crates/hyperswitch_domain_models/src/business_profile.rs	Analyzed
✔️	crates/diesel_models/src/business_profile.rs	49.43% smaller
✔️	crates/diesel_models/src/merchant_account.rs	Analyzed
✔️	crates/diesel_models/src/merchant_connector_account.rs	Analyzed
✔️	crates/diesel_models/src/schema.rs	Analyzed
✔️	crates/diesel_models/src/schema_v2.rs	32.35% smaller