Bug: [BUG] Docker Compose dev environment fails to setup hyperswitch-server



### Bug Description

`hyperswitch-hyperswitch-server-1` container stops abruptly without spinning up the server.  Container can't find `protobuf-compiler` debian package and fails. Below are the logs of the container
```shell
➜  hyperswitch git:(main) docker logs hyperswitch-hyperswitch-server-1            

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package protobuf-compiler
```

Protobuf compiler mentioned here https://github.com/juspay/hyperswitch/blob/a3c2694943a985d27b5bc8b0371884d17a6ca34d/docker-compose-development.yml#L64

### Expected Behavior

`hyperswitch-hyperswitch-server-1` should run

### Actual Behavior

Container simply exits
```shell
➜  hyperswitch git:(main) docker ps -a
CONTAINER ID   IMAGE                                           COMMAND                  CREATED         STATUS                          PORTS                                                 NAMES
3569baada69f   rust:latest                                     "apt-get install -y …"   3 minutes ago   Exited (100) 3 minutes ago                                                            hyperswitch-hyperswitch-server-1

```

### Steps To Reproduce

1. Clone the repo on a new machine
2. Run `docker compose --file docker-compose-development.yml up -d`

### Context For The Bug

_No response_

### Environment

Are you using hyperswitch hosted version? No
If yes, please provide the value of the `x-request-id` response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:
1. Operating System or Linux distribution: Debian 12


### Have you spent some time checking if this bug has been raised before?

- [X] I checked and didn't find a similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

Yes, I am willing to submit a PR!
diff --git a/docker-compose-development.yml b/docker-compose-development.yml
index cf12982a9bd..3878f880b06 100644
--- a/docker-compose-development.yml
+++ b/docker-compose-development.yml
@@ -59,10 +59,12 @@ services:
 
   ### Application services
   hyperswitch-server:
-    image: rust:latest
-    command: | 
-     apt-get install -y protobuf-compiler && \
-     cargo run --bin router -- -f ./config/docker_compose.toml
+    build:
+      dockerfile_inline: |
+        FROM rust:latest
+        RUN apt-get update && \
+            apt-get install -y protobuf-compiler
+    command: cargo run --bin router -- -f ./config/docker_compose.toml
     working_dir: /app
     ports:
       - "8080:8080"

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Fixes: https://github.com/juspay/hyperswitch/issues/6216

Builds a docker image with protobuf for hyperswitch-server.

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->
Refer here for the issue Fixes: https://github.com/juspay/hyperswitch/issues/6216

## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
docker compose --file docker-compose-development.yml up -d 

## Checklist
<!-- Put an `x` in the boxes that apply -->

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