Fix frontend ci error handling

[hwinther]

Description 💬

Motivation and Context 🥅

How has this been tested? 🧪

• Local build ⚒️
• Local tests 🧪
• (optional) Local run and endpoint tested in swagger 🚀

Screenshots (if appropriate) 💻

Types of changes 🌊

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist ☑️

• The pull request title starts with the jira case number (when applicable), e.g. "TEST-1234 Add some feature"
• The person responsible for following up on requested review changes has been assigned to the pull request
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Highly optional checks, only use these if you have a reason to do so ✔️

• This PR changes the database so I have added the create-diagram label to assist reviewers with a db diagram
• This PR changes platform or backend and I need others to be able to test against these changes before merging to dev, so I have added the deploy-azure label to deploy before merging the PR

Checklist for the approver ✅

• I've checked the files view for spelling issues, code quality warnings and similar
• I've waited until all checks have passed (green check/without error)
• I've checked that only the intended files are changed

[github-actions]

frontend

❌ The following build issues should be fixed:

• ❌ src/pages/about/+Page.tsx(1,1): error TS6133: 'React' is declared but its value is never read.

✅ No linting issues 🎊

[github-actions]

Todo Commenter

.github/actions/frontend-build/action.yml

TODO:

• ,FIXME:,BUG:" Line: 172

FIXME:

• ,BUG:" Line: 172

BUG:

• " Line: 172

---

@hwinther Please take a look 👀