Chore(deps): Update serde-saphyr requirement from 0.0.25 to 0.0.26

[dependabot]

Updates the requirements on serde-saphyr to permit the latest version.

Release notes

Sourced from serde-saphyr's releases.

0.0.26

• UTF-16LE, UTF-16BE, UTF-8 with BOM and UTF-8 without BOM are all supported for the Reader - based methods (stabilized)
• Relaxed from_slice to support borrowed deserialization, aligning its behavior with from_str and from_slice_with_options
• Reduce size of Location data structure in huge_documents mode, using 48 bits only for offsets. This silences Clippy warnings, due these some teams needed to box serde-saphyr Error. The maximal size of documents in huge_documents mode is now 256 Tb that is unlikely a problem (default limit is 4 Gb).
• saphyr-parser-bw, whose primary consumer is serde-saphyr, has been renamed to granit-parser, adjusting serde-saphyr dependencies. The granit-parser crate has undergone a security audit followed by additional hardening.

Merge key handling is now configurable via MergeKeyPolicy. There may be communities that

• Indeed have such a strange keys like << as ordinary, and these are even not quoted, maybe in generated YAML. Handling of this case is supported via AsOrdinary variant.
• Took very strict internal policy disallow merge keys in configurations that is their choice, and want to alert about their presence to automate the code review. Handling them as ordinary may result valid YAML with unexpected result, and would not report the error location properly, so there is an Error variant for this case.
• Have legacy code with merge keys, or see nothing wrong with them (default: Merge)

Commits

• a5c3049 Cleanup
• b60a996 Set release to 0.0.26
• 10d9633 Set release to 0.0.26
• 6953cdd Use granit-parser 0.0.2
• 3fc8004 Remove --locked
• 60253e3 Further documment serde(flatten) is not fully supported.
• abdcc34 Work on solving #106 (#107)
• 5eadd3e Improve test coverage
• 9a70ba0 CI fix
• b28f361 CI fix
• 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)