Allow #markup_unsafe to handle StandardError and notify exception

What does this MR do?

This change makes #markup_unsafe catch StandardError instead of RuntimeError, as our markup renderers are capable of raising errors other than RuntimeError. For example, the exception raised in #195625 (closed) is a TypeError.

It also adds tracking for the exception, so the exception will become visible in Sentry.

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers