feat: adding client id for tracking requests to registry

[vanitabhagwat]

What this PR does / why we need it:
feat: Adding client id for tracking requests to registry

Which issue(s) this PR fixes:
feat: Adding client id for tracking requests to registry
Fixes #

[wparsley-eg]

Couple questions:

1. How does the client input their ID? Is this being populated from the HTTP headers?
2. How is this being persisted? Are we logging the ClientID, or storing it in the registry?

Otherwise, looks fine - would like a test case or two here to show coverage.

[vanitabhagwat]

Couple questions:

1. How does the client input their ID? Is this being populated from the HTTP headers?
2. How is this being persisted? Are we logging the ClientID, or storing it in the registry?

Otherwise, looks fine - would like a test case or two here to show coverage.

1. Clients will configure the ID in their feature_store.yaml. Currently making that change to ml-workflow.
2. It would be added to the request traces in eg-feature-store-registry.

I will work on adding the test cases.