Add remote store protobuf/gRPC definitions

[zehiko]

What

In this PR we aim to define initial version of the V0 storage node APIs in the form of grpc protobuf definition. We also want to:

• settle on code generation
• type conversions (between rerun internal types and grpc types

(currently) Example usage:

use re_storage_types::v0::{
    storage_node_client::StorageNodeClient, RegisterRecordingsRequest
};

...

  let mut client = StorageNodeClient::connect("http://127.0.0.1:51234")
        .await
        .unwrap();

    let resp = client
        .register_recordings(RegisterRecordingsRequest {
            description: "test".to_string(),
            obj_storage:  ObjectStore {
              url: "dna.rd",
              bucket_name: "my_s3_bucket",
            },
            typ: re_storage_types::v0::RecordingType::Rrd.into(),
        })
        .await
        .unwrap()
        .into_inner();

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[github-actions]

Deployed docs

Commit	Link
417f0ce	https://landing-h27xvj3fn-rerun.vercel.app/docs

[teh-cmc]

Nice! A few last things but we're very close.

[teh-cmc]

A comment explaining what this is and why 10ms would be helpful?

[zehiko]

ah, right, these are new fields (2 more incoming in the next rebase) from ewebsock version 0.7. Will add comments.

[teh-cmc]

TODO:

• --check flag for pixi run codegen-rstore #7838