Split Bundle and StaticBundle

[SkiFire13]

Objective

• Splitted off from Bundle refactor - Option bundles and Box<dyn Bundle> #19491
• Split Bundle into one type representing a static set of component types (StaticBundle) and one that will be used for representing a possibly dynamic set of components.

Solution

• Create a new StaticBundle type, mirroring Bundle for now
• Switch all APIs that need to statically know the components in a Bundle (i.e. from its type) to use StaticBundle
• Add &self parameters to Bundle to ensure all APIs that use it have a concrete instance to work with in the future.

Additional notes

For now this doesn't do anything functionally, as Bundle still requires the components to be statically fixed. However this opens the doors for changes to the Bundle trait that allow dynamic components without impacting APIs that actually rely on static components.

[ElliottjPierce]

Looks good to me. The parallel contents of code for StaticBundle vs Bundle is kinda annoying, but I know that's changing in the next prs, so I'm not worried about it.