[ENH] Add proto conversions for RequestMetadata

[HammadB]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Adds RequestVersionContext from [ENH] Add version context in python #2827 to all segment type queries.
• New functionality
  • None

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

None

[HammadB]

• [ENH] Add retry on mismatch #2843
• [ENH] Propagate error codes through rust services #2842
• [ENH] Propagate version through system #2839
• [ENH] Add proto conversions for RequestMetadata #2831 👈
• [ENH] Add version context in python #2827 : 1 other dependent PR (#2828 )
• [ENH] Add log position to FE #2826
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @HammadB and the rest of your teammates on Graphite

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[sanketkedia]

nit: log_offset is the name used everywhere else. Don't have any strong preference on which is better but should we have a consistent naming everywhere?

[HammadB]

We should. But this inconsistency is not introduced here (i.e "name used everywhere else" is not true").

If you look at message Collection {} for example

message Collection {
  string id = 1;
  string name = 2;
  string configuration_json_str = 3;
  optional UpdateMetadata metadata = 4;
  optional int32 dimension = 5;
  string tenant = 6;
  string database = 7;
  int64 log_position = 8;
  int32 version = 9;
}

It is log_position. I went off what the collection called it, I don't know how to choose haha.

[HammadB]

Merge activity

• Sep 25, 1:54 PM EDT: @HammadB started a stack merge that includes this pull request via Graphite.
• Sep 25, 2:00 PM EDT: Graphite rebased this pull request as part of a merge.
• Sep 25, 2:01 PM EDT: @HammadB merged this pull request with Graphite.