Filter strings that cannot be parsed as Regex no longer cause an SDK crash

[adinauer]

📜 Description

Fix exception when creating FilterString from string that cannot be parsed as regex.
This was the case e.g. for ignoredErrors, ignoredTransactions, ignoredCheckIns
Catch exception from Pattern.compile and skip using the pattern in that case.

💡 Motivation and Context

Fixes #4212

💚 How did you test it?

📝 Checklist

• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	369.08 ms	416.66 ms	47.58 ms
Size	1.58 MiB	2.21 MiB	641.82 KiB

Previous results on branch: fix/filter-string-regex-error

Startup times

Revision	Plain	With Sentry	Diff
86bce89	382.34 ms	425.34 ms	43.00 ms

App size

Revision	Plain	With Sentry	Diff
86bce89	1.58 MiB	2.21 MiB	641.82 KiB

[stefanosiano]

maybe worth raising the level to Warning?

[adinauer]

Could also be intentional that a filter String isn't meant as a regex and just contains chars not applicable for a regex. I wouldn't consider that something worth WARNING about.