[full-ci] feat: [OCISDEV-541] add crash page

[LukasHirt]

Description

We've added a crash page to the application. This page is displayed when the application encounters an error that it cannot recover from. The first such error we are catching is when spaces loading fails.

Motivation and Context

Handle errors that the app cannot recover from instead of showing the UI in a "stuck" state.

How Has This Been Tested?

• test environment: macos v26.2, chrome v143.0.7499.170
• test case 1: trigger API error when loading spaces

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 change)
• Technical debt
• Tests
• Documentation
• Maintenance (e.g. dependency updates or tooling)

[LukasHirt]

@nirajacharya2 can you please review the new tests? THX

[LukasHirt]

both tests are not working for me locally

- navigating to "/crash?errorCode=RUNTIME-BOOTSTRAP-040", waiting until "load"

This error is strange as it should use the base URL and not only path...

[nirajacharya2]

it will be better to pass user to function. if we logged in with brian this test would have failed

Suggested change

	errorCode: string
	}) {
	const { page } = actorsEnvironment.getActor({ key: 'Alice' })
	return page.goto(`${config.baseUrl}/crash?errorCode=${errorCode}`)
	errorCode: string
	user: string
	}) {
	const { page } = actorsEnvironment.getActor({ key: user })
	return page.goto(`${config.baseUrl}/crash?errorCode=${errorCode}`)

[LukasHirt]

I did slightly different behaviour where I am passing the page directly. Saves one extra param and when doing multiple steps, we get the page from the actor only once instead of inside every step. Let me please know whether this change is fine.

[nirajacharya2]

test code looks good to me

[mzner]

do we need to improve accessibility for this one? I guess some users won't be able to understand the connection between the error and the code. What do you think?

[LukasHirt]

For now, the error is there only for us. I.e. if we get a bug report, we know the code and know right away into which part of the code we should look into. In the future, we might consider adding some documentation where the codes could be listed and users/admins could orient themselves but as since we haven't got any error codes correlating with errors that the users could "fix" themselves I don't see too much value in doing that now.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Condition Coverage on New Code (required ≥ 50%)
1 New Bugs (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE