Bug: [CHORE]: update docker compose toml 



### Feature Description

remove the network_tokenization_service config

### Possible Implementation

remove the network_tokenization_service config

### Have you spent some time checking if this feature request 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/config/docker_compose.toml b/config/docker_compose.toml
index 698800f082d..f0d44db4d5e 100644
--- a/config/docker_compose.toml
+++ b/config/docker_compose.toml
@@ -597,15 +597,5 @@ recon = "recon@example.com"
 [network_tokenization_supported_card_networks]
 card_networks = "Visa, AmericanExpress, Mastercard"
 
-[network_tokenization_service]
-generate_token_url= ""
-fetch_token_url= ""
-token_service_api_key= ""
-public_key= ""
-private_key= ""
-key_id= ""
-delete_token_url= ""
-check_token_status_url= ""
-
 [network_tokenization_supported_connectors]
 connector_list = "cybersource"

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

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

## Description
<!-- Describe your changes in detail -->
remove the network_tokenization_service from the config
![image](https://github.com/user-attachments/assets/fc2f85f5-656c-4d80-b756-fa3b84f2d20b)


### 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).
-->


## 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)?
-->
Test is not required

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

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