Merge main into 0.1 release branch

[luca-della-vedova]

This PR just brings in the latest changes from main into the release-0.1 branch. Specifically, to unblock downstream migrations on rmf_site we need the DeliveryLabel macro PR #30, which is not released.

Eventually I'd like to bring the change all the way to the release-0.2 branch for Bevy 0.14 migration, I thought the sequence would be a main -> 0.1, followed by a 0.1 -> 0.2` but I might have missed something

[mxgrey]

Looks like we'll need to remove the 1.75 test for this branch or else the CI will always be red.

I anticipate we'll need to keep targeting important features at v0.0.x for them to be hypothetically build farm compatible.

[luca-della-vedova]

Agreed! I suspect this PR should not be squash merged but normal merged to preserve history? If that is the case should I amend / force push the merge commit to avoid minor changes (specifically to fix the style) or create a Fix Style commit?
Removing the CI should probably still be a separate commit to keep track of the change

[mxgrey]

Yeah, regular commit makes sense. The hard part will be remembering to switch the mode when the time comes.