fix(deps): update rust crate schemars to v1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
schemars (source)	dependencies	major	0.8 -> 1.0

---

Release Notes

GREsau/schemars (schemars)

v1.0.4

Compare Source

Fixed

• Fix JsonSchema impl on atomic types being ignored on non-nightly compilers due to a buggy cfg check (https://github.com/GREsau/schemars/issues/453)
• Fix compatibility with minimal dependency versions, e.g. old(-ish) versions of syn (https://github.com/GREsau/schemars/issues/450)
• Fix derive for empty tuple variants (https://github.com/GREsau/schemars/issues/455)

v1.0.3

Compare Source

Fixed

• Fix compile error when a doc comment is set on both a transparent (or newtype) struct and its field (https://github.com/GREsau/schemars/issues/446)
• Fix json_schema!() macro compatibility when used from pre-2021 rust editions (https://github.com/GREsau/schemars/pull/447)

v1.0.2

Compare Source

Fixed

• Fix schema properties being incorrectly reordered during serialization (https://github.com/GREsau/schemars/issues/444)

v1.0.1

Compare Source

Fixed

• Deriving JsonSchema with no_std broken due to std::borrow::ToOwned trait not being in scope (https://github.com/GREsau/schemars/issues/441)

v1.0.0

Compare Source

This is a major release with many additions, fixes and changes since 0.8 (but not many since 0.9). While the basic usage (deriving JsonSchema and using schema_for!() or SchemaGenerator) is mostly unchanged, you may wish to consult the migration guide which covers some of the most significant changes.

Changes since 1.0.0-rc.2:

Added

• #[schemars(bound = ...)] attributes are now used from fields as well as containers
• The Schema::pointer(...) method now works when given a JSON pointer in URI Fragment representation with a leading # character. In particular, this means that you can now lookup a schema from a $ref value using that method.

Fixed

• Schema names that contain special characters are now correctly encoded when used inside a $ref value (https://github.com/GREsau/schemars/pull/436)
• Optimise type param usage in SchemaGenerator::subschema_for, reducing LLVM line count and improving compile times (https://github.com/GREsau/schemars/pull/439)

v0.9.0

Compare Source

This version is identical to 1.0.0-alpha.18, but is available for those who are unable to unwilling to use a pre-release version.

Those upgrading from Schemars 0.8 may want to consult the migration guide, which also applies when migrating from 0.8 to 0.9.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `schemars`.
    ... required by package `image-cve-policy v0.1.0 (/tmp/renovate/repos/github/kubewarden/image-cve-policy)`
versions that meet the requirements `^1.0` are: 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0

package `image-cve-policy` depends on `schemars` with feature `impl_json_schema` but `schemars` does not have that feature.


failed to select a version for `schemars` which could resolve this conflict