[TEST] Add error boundary components and exception logging

[fluiddot]

Related PRs:

• [TEST] [Gutenberg] Error boundary and log JS exceptions WordPress-iOS#22654
• [TEST] [Gutenberg] Error boundary and log JS exceptions WordPress-Android#20435

This PR is only for testing purposes. It's a test branch of #6655 that includes forcing JavaScript exceptions.

To test

Note

Use the following installable builds for testing:

• Android
• iOS

Block-level error boundary

1. Create a post.
2. Add an Image block.
3. Observe that the block is not rendered and an error message is displayed instead.
4. Go to Sentry and check errors generated in the last hour for the environment a8cBranchTest (link).
5. Observe that a new Sentry event is registered with name Error in Image block.
6. Navigate to the Sentry event and observe the following items:
   1. The stack trace is symbolicated and points to the correct code line (reference).
   2. It contains a tag with the Gutenberg Mobile version.
   3. The event context contains information about React Native (e.g. version).

Editor-level error boundary

1. (Continue from above test case)
2. Switch to the HTML mode.
3. Observe that the editor stops rendering content and shows an error message instead.
4. Go to Sentry and check errors generated in the last hour for the environment a8cBranchTest (link).
5. Observe that a new Sentry event is registered with name Error in editor (reference).
6. Navigate to the Sentry event and observe the following items:
   1. The stack trace is symbolicated and points to the correct code line.
   2. It contains a tag with the Gutenberg Mobile version.
   3. The event context contains information about React Native (e.g. version).

Unhandled crash

Note

The unhandled error is generated as a side effect of forcing the error in the HTML mode editor.

1. (Continue from above test case)
2. Tap on the ... button located in the top bar.
3. Observe that the app crashes.
4. Open the app again.
5. Go to Sentry and check errors generated in the last hour for the environment a8cBranchTest (link).
6. Observe that a new Sentry event is registered with name Cannot read property 'replace' of undefined.
7. Navigate to the Sentry event and observe the following items:
   1. The stack trace is symbolicated and points to the correct code line.
   2. It contains a tag with the Gutenberg Mobile version.
   3. The event context contains information about React Native (e.g. version).
   4. The error is marked as unhandled.
8. Observe that there's also a RCTFatalException Sentry event with information about the native crash.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.