Update Redocly to Realm v0.115.0 and fix some related issues

[mDuo13]

• Fixes an issue introduced by Prevent maintenance issues when adding faucet hosts and fix the loader #2934 where the loading animation is always visible in interactive tutorials
• Fix a broken image path in stablecoin settings page in Japanese
• Remove redundant loader component from dev tools page

Supersedes #2892.

Known issue, Redocly build reports this:

[error] [1] File /js/tutorials/how-tos/use-tickets.js does not exist
at ./@l10n/ja/docs/tutorials/how-tos/manage-account-settings/use-tickets.md:1:1

But as best I can tell all the references to use-tickets.js in that file (the Japanese use-tickets.md) are absolute paths so it seems like a Redocly bug. The error message was incorrect, but there was a real path issue behind it and I've fixed it.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@redocly/[email protected] 🔁 npm/@redocly/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+548	377 MB	marshevskyy
npm/[email protected] 🔁 npm/[email protected]	None	0	22.7 MB	typescript-bot

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], pypi/[email protected], pypi/[email protected], pypi/[email protected], pypi/[email protected]

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[mDuo13]

@SocketSecurity ignore npm/[email protected]

[amarantha-k]

lgtm