Feature/3257 - Unassign transactions on report coverage change

[sasha-dresden]

Issue FECFILE-3257

API PR2294

• Moved Feature Flags into an Injection Token so we don't directly access the environment throughout our application and to clearly identify that these are feature flags as opposed to general environment configuration settings
• Update name of unassigned transactions feature flag from showAllTransactionsPage to enableUnassignedTransactions as it is no longer specifically about showing/hiding that page.
• Add Shared Form3 Service function getTransactionsOutsideCoverage which gets a count of the transactions that would be outside the coverage range
• Update saving an edit Form3/Form3X to confirm with user before proceeding if any transactions fall outside the range.

[danguyf]

So far everything works in my local testing except the newly unassigned transactions are not showing up on the Transactions page. Am I doing it wrong?

[danguyf]

Everything is working correctly for me.

I believe the final AC ("Then those transactions will be unassigned with that report and display in TRANSACTIONS.") is being implemented in FECFILE-1819 not here.

Merge conflicts to resolve.

[toddlees]

nice clarification!

[sonarqubecloud]

Quality Gate failed

Failed conditions
77.4% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud