feat(business_profile): introduce domain models for business profile v1 and v2 APIs

[SanchithHegde]

Type of Change

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

Description

This PR includes the following changes:

1. Refactors code to ensure that all updates to the business_profile table always include an update of the modified_at field.
2. Introduces the BusinessProfileUpdate::RoutingAlgorithmUpdate for use in routing code and to slightly improve code readability.
3. Updates the apply_changeset() method on BusinessProfileUpdate to use fields from the source object for fields which are not being updated.
   • This function is only called in the BusinessProfileInterface implementation for MockDb, so this should not affect production code.
4. Adds database migrations for business profile v2, and introduces corresponding types (and feature flags) in the diesel_models and common_enums crates.
5. Introduces business profile v1 and v2 types (and feature flags) in the hyperswitch_domain_models crate.
   • The code has not been updated to make use of either of these domain models anywhere. The refactor to use business profile v1 domain models throughout the codebase will be taken up in a separate PR, since it affects a lot of files.

To reiterate, this PR does not affect any production code, and only adds new code, while moving existing code behind suitable feature flags.

Additional Changes

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

This PR includes database migrations for and updates schema for business profile v2 APIs, does not affect business profile v1 schema.

Motivation and Context

Enabling / unblocking business profile v2 changes or any other changes dependent on business profile v2 types.

How did you test it?

Ran the following commands and ensured they've passed:

# Ensuring successful compilation of v1 and v2 diesel models
cargo clippy -p diesel_models
cargo clippy -p diesel_models --no-default-features --features v2,business_profile_v2

# Ensuring successful compilation of v1 and v2 domain models
cargo clippy -p hyperswitch_domain_models
cargo clippy -p hyperswitch_domain_models --no-default-features --features v2,business_profile_v2

# Ensuring clippy passes as usual
just clippy

Attaching a screenshot of the same:

In addition, I've done sanity testing using 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