chore(deps): Update Rust crate yaml-rust2 to 0.9

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
yaml-rust2	dependencies	minor	0.8 -> 0.9

---

Release Notes

Ethiraric/yaml-rust2 (yaml-rust2)

v0.9.0

Compare Source

Breaking Changes

• Update dependencies.
  Since hashlink is exposed (through Yaml::Hash) and has been updated from
  0.8.4 to 0.9.1, the new version of yaml-rust2 will not link properly if you
  explicitly rely on hashlink v0.8.
  Existing code with v0.8.4 should still compile fine in v0.9.1 (see
  hashlink's v0.9.0
  changelog).

Bug fixes

• (#​37)
  Parse empty scalars as "" instead of "~".

Features

• Add Yaml::is_hash.
• Add better doccomments to the Index and IntoIterator implementations for
  Yaml to better explain their quirks and design decisions.

v0.8.1

Compare Source

Bug fixes

• (#​29) Fix parsing
  failing for deeply indented scalar blocks.

• (#​21-comment)
  Fix parsing failing with comments immediately following a YAML tag.

Features

• (#​19) Yaml now
  implements IndexMut<usize> and IndexMut<&'a str>. These functions may not
  return a mutable reference to a BAD_VALUE. Instead, index_mut() will
  panic if either:

  • The index is out of range, as per IndexMut's requirements
  • The inner Yaml variant doesn't match Yaml::Array for usize or
    Yaml::Hash for &'a str

• Use cargo features

  This allows for more fine-grained control over MSRV and to completely remove
  debug code from the library when it is consumed.

  The encoding feature, governing the YamlDecoder, has been enabled by
  default. Users of @davvid's fork of yaml-rust or of yaml-rust2 might
  already use this. Users of the original yaml-rust crate may freely disable
  this feature (cargo <...> --no-default-features) and lower MSRV to 1.65.0.

• Duplicate keys no longer allowed

  Instead of silently choosing one of two values sharing the same key in a
  mapping, we now issue an error. This behavior is part of the YAML
  specification, but not tested by the yaml-test-suite (the parser needs to
  emit events for both key-values). Additionally, there is no standard way of
  defining which value should be chosen in case of a duplicate.

---

Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coveralls]

Pull Request Test Coverage Report for Build 11624535279

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 62.993%

---

Totals
Change from base Build 11488444135:	0.0%
Covered Lines:	943
Relevant Lines:	1497

---

💛 - Coveralls