Bug: refactor(euclid): update proto file for elimination routing




diff --git a/proto/elimination_rate.proto b/proto/elimination_rate.proto
index c5f10597ade..d585dd2494b 100644
--- a/proto/elimination_rate.proto
+++ b/proto/elimination_rate.proto
@@ -28,8 +28,17 @@ message EliminationResponse {
 
 message LabelWithStatus {
     string label = 1;
-    bool is_eliminated = 2; 
-    string bucket_name = 3;
+    EliminationInformation elimination_information = 2;
+}
+
+message EliminationInformation {
+    BucketInformation entity = 1;
+    BucketInformation global = 2;
+}
+
+message BucketInformation {
+    bool is_eliminated = 1;
+    repeated string bucket_name = 2;
 }
 
 // API-2 types
@@ -64,4 +73,4 @@ message InvalidateBucketResponse {
         BUCKET_INVALIDATION_FAILED = 1;
     }
     InvalidationStatus status = 1;
-}
\ No newline at end of file
+}

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

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

## Description
<!-- Describe your changes in detail -->
This will update the proto file for elimination routing to include the global rates. This is basically done in order to keep the proto file upto-date with dynamic routing service.

### 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)?
-->
Testing isn't required as this is only env change

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

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