build: Bump serde-saphyr from 1.1.0 to 1.2.0 in /crates/core/fuzz

[dependabot]

Bumps serde-saphyr from 1.1.0 to 1.2.0.

Release notes

Sourced from serde-saphyr's releases.

1.2.0 It's all about !!tags this time

This release focuses on enhanced tag support.

• Implemented tag capturing (#183). Applications can use custom tags to express units, priorities, accessibility, or other application-specific semantics for a node. This is supported by new Tagged<T> wrapper that is similar to Commented<T>.
• Unsupported tags can now be rejected rather than ignored (new option reject_unsupported_tags, #180). This aligns the behavior with ruamel.yaml that rejects tags for which it has no constructor (serde-saphyr does not construct this way) that caused discussion on prek.
• Clearly wrongly placed tags like !!int [1] or !!map [1] are now an error.
• Documentation was revised to make sure all examples compile (are not fragments).

Changelog

Sourced from serde-saphyr's changelog.

1.2.0 Maintenance release

Changed

• Folded property-interpolation depth and work limits into Budget; property resource-limit failures are now reported through Error::Budget and BudgetBreach.
• Added the opt-in Options::reject_unsupported_tags strict mode. It rejects explicitly tagged scalar, sequence, and mapping nodes when their tag is unknown to serde-saphyr; the default remains permissive for compatibility with custom tagged enums. YAML 1.1 !!merge and !!value are accepted in this mode only as the exact scalar mapping keys << and =, respectively, while robotics-only !degrees and !radians require both the robotics crate feature and angle_conversions, and !include requires both the include crate feature and a configured resolver.
• Enforced the scalar, sequence, or mapping node kinds required by recognized tags even when reject_unsupported_tags is disabled.
• Hardened serializer indentation handling: indent_step is now limited to 1..=64, all serializer entry points validate it, and indentation arithmetic returns an error instead of overflowing. We do not consider this breaking because values outside this range does not look sane.
• Validated custom anchor-generator names before emission. Names must be 1–256 bytes and cannot contain whitespace, control characters, or YAML flow punctuation; unsupported names now return a serialization error.

Fixes

• Avoided unnecessary quotes around string keys and values containing an inline #, such as a#b, while retaining quotes for leading or whitespace-separated hashes. Borrowed from commit 1119a54 under the terms of the Apache/MIT licenses. When property interpolation is configured, newly plain values such as ${NAME}#fragment can interpolate; use quote_all to preserve literal values.
• Recognized explicit YAML 1.1 !!merge keys, including verbatim tags and %TAG-expanded handles, everywhere implicit << merge keys are supported.
• Recognized the YAML 1.1 !!value tag while intentionally treating it as a no-op annotation.
• Accepted valid zero-indented root folded block scalars, including #-prefixed content lines.
• Fixed externally tagged typetag trait-object deserialization by consuming the closing mapping event when a Serde map visitor returns after its final key/value pair, preventing a false "multiple YAML documents" error.
• Rejected non-UTF-8 canonical include and root-file paths before resolver policy checks and source identity handling, preventing lossy path collisions and policy bypasses on Unix.
• Reported alias-use locations as primary for unsupported-tag and budget failures during replay, while retaining the anchor-definition locations as secondary context.

Testing

• Reviewed yaml test suite, made sure all 350 active IDs and all 402 active cases are represented and documented we use YAML Test Suite v2022-01-17.
• property test with 1,024 generated cases to check the round trip.
• added tests for typetag.

Commits

• 4504205 Disable test miri cannot run
• db2ce54 Formatting fix
• d7e0a6d Formatting fix
• 34b008c Last README.md tweaks
• cb230e8 Last README.md tweaks
• d3f1d38 Last README.md tweaks
• e54e52a Merge remote-tracking branch 'origin/master'
• 4279ed4 Prepare for release 1.2.0
• 99262cc Improve test coverage
• ea3333b Bump granit-parser from 07e0097 to 53104a5 (#187)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jaanisoe]

Closing. The cargo-fuzz crate is a separate workspace, so a bump here edits the root manifest and leaves the root lockfile stale. Dependabot cannot produce a mergeable version of this. Version updates are now off, see #18.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.