Tracking: Take advantage of ComponentId's being discoverable before registration

[ElliottjPierce]

What problem does this solve or what need does it fill?

Lots of planned and wishlist features require (or would benefit from) knowing a component or resource's ComponentId before it is registered. Effectively, we can reserve an id with only &Components and know that the id will be the same id it receives when registered. Further, we can also queue a registration to happen with only &Components, which provides additional flexibility.

This is very useful for assets as entities (#11266), multi-world bevy, readonly queries and other readonly system parameters, pre-registering components, scripting, (and probably more).

History

This is a better alternative for #18155.

Roadmap

• Decouple registration from storage. See Isolate component registration #17671.
• Implement queued registration. See Queued component registration #18173.
• Allow readonly queries and system parameters to be initialized with only &World. #18276
• Allow creating and running read-only systems with only &World.
• Remove try_query API (no longer needed).

After #18173, parallel work may begin on components as entities and assets as entities.