CPLAT-5397: Add isErrorBoundary argument to the @Component2 annotation

[tainhenning-wk]

Motivation

Add isErrorBoundary argument to the new @Component2() annotation, allowing the use of the componentDidCatch and getDerivedStateFromError lifecycle methods. This makes it possible for custom components to act as React error boundaries instead of having to be wrapped by the default ErrorBoundary HOC.

Changes

Added isErrorBoundary argument
Added skipMethods override
Added tests

Release Notes

Allow custom components to act as React error boundaries.

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Client Platform member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary2-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[aaronlademann-wf]

Good start @tainhenning-wk !

[aaronlademann-wf]

+1

[aaronlademann-wf]

+1 refresh

[joebingham-wk]

+1

[aaronlademann-wf]

QA +1

[aaronlademann-wf]

@Workiva/release-management-pp