Sanity-check that an archetype has a component

[emilk]

What

We're starting to build in a lot of assumptions in our code about what archetypes has what components.
This happens here and there where we query for components directly.

At first I added the checks at runtime using reflection, before I realized we can do it at compile-time instead:

    fn _check_encoded_image_has_blob(image: &archetypes::EncodedImage) {
        let _: components::Blob = image.blob;
    }

This means we will be reminded to update the code if we ever change the archetype to e.g. use a EncodedImageBuffer component or similar in the future!

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.

[abey79]

Nice. Feels like this is very close to warrant a dedicated macro.

[emilk]

A macro is a good idea 🤔