Bug: Removal of routing_metadata Logs



### Bug Description

The logs about the field not being deserialized was being spammed.

### Expected Behavior

It should do a checked deserialization of the metadata.

### Actual Behavior

It is spamming logs for every payments.

### Steps To Reproduce

1. Configure routing rules
2. Make a payment
3. Check logs

### Context For The Bug

_No response_

### Environment

Are you using hyperswitch hosted version? Yes/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:
2. Rust version (output of `rustc --version`): ``
3. App version (output of `cargo r --features vergen -- --version`): ``


### 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/crates/router/src/core/payments/routing.rs b/crates/router/src/core/payments/routing.rs
index 8c27e3b3cac..d1a5441d958 100644
--- a/crates/router/src/core/payments/routing.rs
+++ b/crates/router/src/core/payments/routing.rs
@@ -115,10 +115,7 @@ pub fn make_dsl_input_for_payouts(
         .transpose()
         .change_context(errors::RoutingError::MetadataParsingError)
         .attach_printable("Unable to parse routing_parameters from metadata of payouts")
-        .unwrap_or_else(|err| {
-            logger::error!(error=?err);
-            None
-        });
+        .unwrap_or(None);
     let payment = dsl_inputs::PaymentInput {
         amount: payout_data.payouts.amount,
         card_bin: None,
@@ -249,10 +246,7 @@ where
         .transpose()
         .change_context(errors::RoutingError::MetadataParsingError)
         .attach_printable("Unable to parse routing_parameters from metadata of payment_intent")
-        .unwrap_or_else(|err| {
-            logger::error!(error=?err);
-            None
-        });
+        .unwrap_or(None);
 
     Ok(dsl_inputs::BackendInput {
         metadata,
@@ -937,10 +931,7 @@ pub async fn perform_session_flow_routing(
         .transpose()
         .change_context(errors::RoutingError::MetadataParsingError)
         .attach_printable("Unable to parse routing_parameters from metadata of payment_intent")
-        .unwrap_or_else(|err| {
-            logger::error!(?err);
-            None
-        });
+        .unwrap_or(None);
 
     let mut backend_input = dsl_inputs::BackendInput {
         metadata,
@@ -1166,10 +1157,7 @@ pub fn make_dsl_input_for_surcharge(
         .transpose()
         .change_context(errors::RoutingError::MetadataParsingError)
         .attach_printable("Unable to parse routing_parameters from metadata of payment_intent")
-        .unwrap_or_else(|err| {
-            logger::error!(error=?err);
-            None
-        });
+        .unwrap_or(None);
     let payment_method_input = dsl_inputs::PaymentMethodInput {
         payment_method: None,
         payment_method_type: None,

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

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

## Description
<!-- Describe your changes in detail -->
Removal of metadata_parsing logs, as it was being spammed a lot of times. Moreover soon a method for proper deserialization by either String match or conversion of the hashMap to typed will be done.

### 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)?
-->
We are just removing logs in this PR.
No extra code/flow changes.

## 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`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
