Filings UI - Unit Testing Tech Debt for ToDo list Expansion Panel content and recent filings

## What is the problem?
* We have a lot of empty tests for our more recent filing/task additions
* We have extremely large test files that need to be refactored/parameterized to support the varying entity types we now support

## What is the impact?
* Regression testing / incoming changes are at risk of causing a break that could otherwise be caught in the CI pipeline.

## Proposed solution
* We spend some time refactoring the unit testing coverage to be parameterized so we can test varying entities and the new inclusions of data in our ToDo lists and Filings History List.

Start by locating the Filings UI unit-test files and identifying the empty tests and oversized test suites for the ToDo list Expansion Panel and recent filings. Review existing coverage for varying entity types; done means parameterized tests cover the new ToDo and Filings History data and protect against regressions in CI.

Written by the indexing model from the issue text.