Provide a more structured dependency injection framework for components

[cbeer]

Straw-man for future discussion. The hope and dream is a slightly more structured + formal dependency injection framework could make support for multiple UI frameworks (e.g. Bootstrap 5 + 6) more possible and ease one barrier for upgrading.

TODO:

• build out + extract some of the system/"component library" UI components, anticipating that could handle most of the Bootstrap 5 -> 6 pain.
• align injected components with the "right" level (not too high-level as to be exhausting to customize, not so low-level that we end up with a large number of injection points)
• align the parameters to injected components for greater consistency (e.g. all document-keyed components get a document presenter on an expected key)
  • extract a search presenter that encapsulates the search parameters, solr response, and config
    • extract a configuration presenter that will let us pass the whole configuration around, without losing context-specific information (Extract Blacklight::ContextualConfigurationPresenter #3838)
• maybe nice to pull the components configuration up to the top-level of configuration?