Implement Composition API

## Description (Hypothesis):
Convert all the UI's from options API to Composition API

* What are the most critical features being built as part of this Epic
* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

----
## Acceptance Criteria
* When all the UI's have been converted over to the composition API

----
## 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

No files, tests, or entry points are named. Start by inventorying the repository's UI code and identifying components still using the Options API, then determine the conversion scope and dependencies. Done means all UI components have been converted to the Composition API and the existing UI behavior remains intact.

Written by the indexing model from the issue text.