Make API handling on the FE consistent app wide

[dumathane]

Current Experience

Proposed Change

We need to level up to an intentional and repeated paradigm for how user input is not lost unintentionally, api communication takes place, snackbars are provided, abort controllers are handled, and users are provided app freedom and notified of action success/failures.

Why Should We Prioritize?

Providing some consistency will drastically reduce the following:
-App inconsistency
-Silent failure potential
-Silent unintentional success potential
-Mistakenly lost input data
-'Locked up' waiting for API responses
-uses of loading/saving/submitting/deleting pages

Testing Considerations

Checklist

• Add the relevant team label (Health, global, design system, API, Qa and Release etc.)
• Attach to ticket to the relevant Team Tech Debt Epic epic (old frontend engineering epic is no longer in use as each team is managing their code's technical debt and code upkeep work)