feat: add hsdev binary to run migrations

[davidkurilla]

Type of Change

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

Description

This PR closes #4589
Created a new Rust binary in the crates directory which automates the Diesel migrations with Postgres. The new tool is a CLI tool that takes a path to a TOML file as an argument along with the name of a TOML table to extract Postgres database credentials from. The tool then automatically performs the migrations by utilizing diesel_migrations library. From our testing, we were able to set up Hyperswitch locally without using diesel_cli and Bash variables on WSL2 Ubuntu.

I worked on this Issue with @JamesM25 @ind1goDusk

The example below shows the application running using cargo run in the hsdev crate.

cargo run -- --toml-file ~/hyperswitch/config/development.toml --toml-table master_database

Additional Changes

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

Motivation and Context

Before our tool, Hyperswitch needed to be set up on local machines using a long diesel_cli command with Bash variables for the Postgres migration. Now we have provided a simpler and easily repeatable solution to Postgres and Diesel migrations that allows for greater modularity as you can select specific TOML files and tables to select database credentials from.

How did you test it?

We wrote two units test on the core functionality. We tested it both on a dummy TOML file as well as in Hyperswitch repository. We were able to set up Hyperswitch locally using hsdev instead of diesel_cli.

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

[SanchithHegde]

Optional change: you can take advantage of Rust's raw string literals instead of having to escape quotes:

let toml_str = r#"username = "db_user"
password = "db_pass"
dbname = "db_name"
host = "localhost"
port = 5432"#;

[SanchithHegde]

@davidkurilla @JamesM25 Could you also address the failing CI checks?

[SanchithHegde]

@JamesM25 Please address the clippy lints as well. Feel free to reach out if you have any queries about them. As for the failing MSRV check, we can run cargo update -p migrations_macros@2.2.0 --precise 2.1.0, and then commit the Cargo.lock file and push it.