Optimize bcrs-shared-components

## Description (Hypothesis):
- Short Description of the needed Epic in the below format

* As a developer
* I want to easily insert a shared component into any UI
* so that features are easier to build

----
## Acceptance Criteria
* Used to determine whether the implementation is correct and delivers the business benefits

----
## Additional Information
* Start date when team will start to work on: This is visible in ZenHub under "Roadmap"
* End date Epic will be delivered: This is visible in ZenHub under "Roadmap"
* T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints). Story points needs to be updated in Epic. This can be decided by team.
* Process Flow (if applicable)
* CM considerations?
* Possible dependencies or blockers foreseen right now? - Please create a story and block this epic by the dependency story.

----
Enabler Epics:
* action
* result
* object

The issue names bcrs-shared-components but provides no files, tests, entry points, or concrete acceptance criteria. Start by locating the shared-components implementation and defining the intended UI integration scope with the team; completion cannot be verified from the current issue text.

Written by the indexing model from the issue text.