Bug: [FIX] add a metric while pushing data to drainer stream




diff --git a/crates/storage_impl/src/lib.rs b/crates/storage_impl/src/lib.rs
index 7e2c7f2fc3c..d31f05b4979 100644
--- a/crates/storage_impl/src/lib.rs
+++ b/crates/storage_impl/src/lib.rs
@@ -225,6 +225,11 @@ impl<T: DatabaseStore> KVRouterStore<T> {
                     .change_context(RedisError::JsonSerializationFailed)?,
             )
             .await
+            .map(|_| metrics::KV_PUSHED_TO_DRAINER.add(&metrics::CONTEXT, 1, &[]))
+            .map_err(|err| {
+                metrics::KV_FAILED_TO_PUSH_TO_DRAINER.add(&metrics::CONTEXT, 1, &[]);
+                err
+            })
             .change_context(RedisError::StreamAppendFailed)
     }
 }
diff --git a/crates/storage_impl/src/metrics.rs b/crates/storage_impl/src/metrics.rs
index 3310e458879..29bca2a007b 100644
--- a/crates/storage_impl/src/metrics.rs
+++ b/crates/storage_impl/src/metrics.rs
@@ -8,3 +8,5 @@ counter_metric!(KV_MISS, GLOBAL_METER); // No. of KV misses
 // Metrics for KV
 counter_metric!(KV_OPERATION_SUCCESSFUL, GLOBAL_METER);
 counter_metric!(KV_OPERATION_FAILED, GLOBAL_METER);
+counter_metric!(KV_PUSHED_TO_DRAINER, GLOBAL_METER);
+counter_metric!(KV_FAILED_TO_PUSH_TO_DRAINER, GLOBAL_METER);

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

## Description
<!-- Describe your changes in detail -->
Add a metric to indicate data was pushed to drainer

## 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).
-->
Add a proper metrics to indicate data was pushed/failed while pushing to drainer

## 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)?
-->
- Do a transaction through KV merchant
- Check `KV_PUSHED_TO_DRAINER` on grafana keeping data source as `vm-single`
![Screenshot 2024-01-30 at 4 10 56 PM](https://github.com/juspay/hyperswitch/assets/43412619/5c7dbfdc-253f-4895-985a-5bc674a56de4)

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