feat(notifications): add notification api and update banner

[daniel-belcher]

Add parameter for notifications to be added as needed. Update Banner to use this system. Store dismissed locally.

🎫 Linked Ticket

ticket to close
related ticket

💬 Description / Notes

Initial dive into ticket was focused on database for dismissed notifications, as well as a more detailed table for notifications. This was deemed unnecessary and ticket was redone using a simple parameter for notification storage and to switch dismissed notifications to local storage so as not to have a table with User info.

🛠 Changes

• New Lambda endpoint
• Hook for Banner to pull notifications
• Hook for dismissed notifications to be stored locally
• No visual changes atm

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	81.36%	7188 / 8834
🔵	Statements	80.77%	7549 / 9346
🔵	Functions	75.08%	2155 / 2870
🔵	Branches	52.63%	1478 / 2808

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
lib/config/deployment-config.test.ts	94.23%	81.25%	100%	94.11%	62, 71, 118
lib/config/deployment-config.ts	96.66%	93.33%	100%	96.66%	106-108
lib/lambda/getSystemNotifs.ts	0%	0%	0%	0%	4-23
react-app/src/api/useGetSystemNotifs.ts	33.33%	100%	0%	33.33%	6-8, 12-13
react-app/src/components/Banner/MMDLSpaBanner.tsx	9.09%	0%	0%	11.11%	8-19
react-app/src/hooks/useNotifications/index.ts	6.25%	0%	0%	6.66%	11-36

Generated in workflow #1482 for commit 9271f0f by the Vitest Coverage Report Action

[asharonbaltazar]

Should we consolidate these two hooks? Will they ever be used independently?

If yes, we can definitely move all this logic into the hook and let the component just concern itself with presentation