[FRONTEND] Add error boundary to async components

[bcho892]

Is your feature request related to a problem? Please describe.

On new deployments the chunk will be named differently hence we should wrap them in an error boundary

BEFORE MERGING

• [ ] Storybooks created where possible
• [ ] Tested with nock if data fetching
• [ ] Tests written for critical interactions
• [ ] PR Reviewed (For non-trivial changes)
• [ ] Changes tested after rebasing on master or merging in master (hint: git fetch origin master:master, then git rebase master or git merge master)
• [ ] All required PR checks passing