deps: Bump js-yaml from 4.3.1 to 5.4.1

[dependabot]

Bumps js-yaml from 4.3.1 to 5.4.1.

Changelog

Sourced from js-yaml's changelog.

[5.4.1] - 2026-08-26

Changed

• Hard-limit merge sequence size to 100.

Security

• Count empty mappings in merge sequences toward maxTotalMergeKeys to limit CPU usage, #797.

[5.4.0] - 2026-08-25

Added

• Added the scalarStyleRules dumper option to customize string formatting. See Scalar styling for details.

Changed

• [breaking] Flattened the low-level AST node style representation. Scalar and collection nodes now use SCALAR_STYLE and COLLECTION_STYLE values; explicit tags use the separate tagged property. Alias nodes now contain only kind and anchor. This only affects code that directly constructs or edits AST nodes.
• [breaking] The sortKeys option was rewritten using AST mutation to avoid side effects.
• Reworked scalar style selection. This can change formatting without changing loaded values; in particular, whitespace-only strings are now double-quoted.

Fixed

• Accept a byte order mark at the start of each document in a stream, #791.
• Produce valid flow mappings with quoteFlowKeys and flowSkipColonSpace, including alias and property-only keys, #786.
• Preserve empty scalar items when converting block sequences to flow style.
• Do not apply the 1024-character simple-key limit to flow mapping keys.
• Count Unicode code points, rather than UTF-16 code units, for the 1024-character simple-key limit.
• Add an explicit document-end marker after keep-chomped block scalars when needed to preserve trailing newlines.

[5.3.0] - 2026-08-14

This release focuses on reworking the documentation and making small architectural improvements before moving forward.

Added

• Added completely new documentation.
• Exported DUMP_SCHEMA, the default schema used by the dumper.
• Added YAMLException.throwAt() for throwing an error at a source position.

Changed

... (truncated)

Commits

• e5a3ba0 5.4.1 released
• e54dea3 Hard-limit merge sequence size to 100
• dfd3a29 Cleanup 6a8e05f, #797
• 6a8e05f fix: count empty merge sources against maxTotalMergeKeys (#797)
• 6b4ff5e 5.4.0 released
• 3b3625e Update changelog
• 4f25a74 Fix file name
• 3bd003b Expose new scalar styling API
• fbb3e9d Remove regex lookbehind for ES2015 compatibility
• d43c185 Fix flowSkipColonSpace by forcing quoteFlowKeys
• Additional commits viewable in compare view

[matz3]

The comment was already outdated, and with the upgrade to js-yaml v4, it was already removed: SAP/ui5-project#380

However, it seems that another PR (SAP/ui5-project#457), that was started before the upgrade did re-introduce the code/comment again, and referenced jsyaml.DEFAULT_SAFE_SCHEMA which already in js-yaml v4 is undefined, so the default was used.

Are you sure that the CORE_SCHEMA is equivalent to DEFAULT_SAFE_SCHEMA, or rather the default schema of v4, as DEFAULT_SAFE_SCHEMA did not exist anymore in js-yaml v4?

One important aspect of yaml parsing is merge keys (<<:). This is widely used by custom task/middleware configuration (e.g. https://github.com/ui5-community/ui5-ecosystem-showcase/tree/main/packages/ui5-tooling-modules).
We should keep that stable, and it looks like we do not have any tests that verify it.