refactor: migrate to use build_info and log_utils crates for build information and logging framework

[SanchithHegde]

Description

This PR migrates the code to use libraries from the https://github.com/juspay/framework-libs-rs repository, for obtaining the cargo workspace members and the logging framework.

This PR includes the following changes:

• Removes the cargo_workspace module from the build script and uses the build_info crate instead.
• Migrates the logging framework to use the log_utils crate.
• Includes the build version information in logs using vergen crate (enabled via build_info crate).
• Includes the version information in a response header for all responses
• Generates a request ID if not provided in request headers, and also propagates the same to response headers.
• Copies over the .gitignore file as .dockerignore, so that the git working directory is clean when building the Docker image (git status would not report working directory as dirty).

Testing

1. Compared the logs (and fields) for a request on main branch and current branch, and noticed no differences in terms of keys included:

   Request: curl -i http://localhost:3001/

   

   (Tool used: https://semanticdiff.com/online-diff/json/)

2. Ran using command cargo run --features vergen, and confirmed that the build_version field is present in logs:

   

3. Confirmed that the version is included in the response headers when run with the vergen feature enabled:

   $ curl -i http://localhost:3001/
   HTTP/1.1 404 Not Found
   x-version: v0.7.0-7-ge55438ce9a93-dirty
   content-length: 0
   date: Mon, 23 Mar 2026 10:25:20 GMT

4. When no x-request-id header is provided, one is generated automatically and is available in response headers:

   $ curl -i http://localhost:3001/
   HTTP/1.1 404 Not Found
   x-request-id: 019d1c0f-3a9a-7ad3-adda-1f0ed29e15bd
   x-version: v0.7.0-8-gf5c1cbd7738c-dirty
   content-length: 0
   date: Mon, 23 Mar 2026 18:57:33 GMT

   And the same request ID is included in logs:

   {
     "message": "[REQUEST - EVENT] finished processing request",
     // ...
     "request_id": "019d1c0f-3a9a-7ad3-adda-1f0ed29e15bd"
   }

5. When a value is provided in the x-request-id header, it is included in logs and the same is visible in response headers:

   $ curl -H 'x-request-id: test-request-id' -i http://localhost:3001/
   HTTP/1.1 404 Not Found
   x-request-id: test-request-id
   x-version: v0.7.0-8-gf5c1cbd7738c-dirty
   content-length: 0
   date: Mon, 23 Mar 2026 18:58:34 GMT

   {
     "message": "[REQUEST - EVENT] finished processing request",
     // ...
     "request_id": "test-request-id"
   }

P.S.: I intentionally changed the log formatting to use prettified JSON for readability. Otherwise, as per the changes in the PR, using json log format would print compact JSON logs itself, not prettified JSON.

[SanchithHegde]

This is to enable logs for crates in this repo, crates from the framework-libs-rs repo and any additional crates passed in crates_to_filter.

[SanchithHegde]

Let me know if you would prefer this printed to stderr, or not printed at all.

Currently, this line is printed to stdout at the beginning:

[INFO] log_utils: Using console filtering directive: WARN,tartarus=DEBUG,locker=DEBUG,hyperswitch_masking=DEBUG,log_utils=DEBUG,tower_http=DEBUG,build_info=DEBUG

Note that this line is printed as is, even if the JSON formatting is enabled.