Update architecture for easier/faster/safer development (Refactoring)

## Description (Hypothesis):

The current UI architecture has been outgrown due to many extra demands (entity types, filing types).

* As a developer
* I want to be able to easily add new functionality (eg, entity types, filings)
* so that my work is more concise and faster and I don't cause risk to existing code.

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