Automate/simplify setup steps when consuming a Blazor component library

All of the major Blazor component libraries require multiple steps in order to setup their libraries in a Blazor app. Often these steps include:

- Added JavaScript files
- Linking to CSS style sheets
- Registering services in DI
- Adding infrastructure components that enable cross-cutting features
- Adding using directives for namespaces

Are there perhaps some patterns here that we can enable component library authors to automate so that it's easier to consume Blazor components? Are there common framework abstractions we should be adding to Blazor so that component libraries can reuse them and better compose with each other? Is there additional guidance we should provide to help component library authors make their libraries easier to consume?