fix: filter out intentional user-input errors from error-reporting-lamda

[khendrikse]

🎉 Thanks for submitting a pull request! 🎉

Summary

A follow up to this PR to also filter from within the lambda

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures your code follows our style guide and
  passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5e51821b-b086-4403-aa71-25e20722af90

📥 Commits

Reviewing files that changed from the base of the PR and between acaf478 and 2c6882d.

📒 Files selected for processing (1)

• site/netlify/functions/error-reporting.ts

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Improved error detection to identify and properly handle user input validation errors separately from system errors.

Walkthrough

The error-reporting handler is enhanced to detect and filter user-input errors. A new USER_INPUT_ERROR_MESSAGE_PATTERNS constant defines patterns for identifying user input errors, and an isUserInputError(message) function checks whether an error message matches these patterns. When the handler processes incoming error reports, it now checks the parsed JSON message field against these patterns and returns a 200 status code early without notifying Bugsnag if a match is found. All other error handling logic remains unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: filtering out intentional user-input errors from the error-reporting lambda function.
Description check	✅ Passed	The description is related to the changeset, mentioning it as a follow-up to a previous PR to filter user-input errors from within the lambda.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch EX-2080/filter-out-intentional-user-input-errors-in-lambda

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

📊 Benchmark results

Comparing with acaf478

• Dependency count: 1,061 (no change)
• Package size: 355 MB (no change)
• Number of ts-expect-error directives: 356 (no change)