deps(deps): bump x509-cert from 0.2.5 to 0.3.0

[dependabot]

Bumps x509-cert from 0.2.5 to 0.3.0.

Commits

• c478c6b x509-cert v0.3.0 (#2375)
• 905717f der v0.8.1 (#2377)
• 2556627 der: cap maximum number of nested messages at 64 (#2379)
• b45caa8 der: have SliceReader use reader::position::Position (#2378)
• 42b4325 x509-cert: re-enable minimal-versions checks (#2374)
• 233eb65 chore(deps): bump the all-deps group across 1 directory with 8 updates (#2373)
• f9e2ab5 chore(deps): bump crate-ci/typos from 1.47.2 to 1.48.0 (#2372)
• 4bfdd7c chore(deps): bump p256 from 0.14.0-rc.15 to 0.14 (#2371)
• 235839f tls_codec: 0.4.3 prep (#2365)
• de2aa55 der: simplify SetOfVec sorting test (#2367)
• 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)

[proggeramlug]

Validated locally on macOS: this does not compile. cargo check --workspace --all-targets
(host-compatible scope) is green on origin/main and fails with 4 errors on this branch,
all in crates/perry-ext-node-forge/src/crypto.rs. x509-cert 0.3 is a breaking release and
this PR bumps the version without adapting the call sites.

error[E0432]: unresolved import `der::flagset`
   --> crates/perry-ext-node-forge/src/crypto.rs:21:10
    | use der::flagset::FlagSet;
note: found an item that was configured out

error[E0432]: unresolved import `x509_cert::ext::AsExtension`
  --> crates/perry-ext-node-forge/src/crypto.rs:35:5
   | no `AsExtension` in `ext`

error[E0423]: cannot initialize a tuple struct which contains private fields
   --> crates/perry-ext-node-forge/src/crypto.rs:242:19
    | rdns.push(RelativeDistinguishedName(set));

error[E0423]: cannot initialize a tuple struct which contains private fields
   --> crates/perry-ext-node-forge/src/crypto.rs:244:8
    | Ok(RdnSequence(rdns))

Three distinct adaptations are needed:

1. der::flagset is now behind a feature that is off in this resolution — the der
   dependency needs its flagset feature enabled ("found an item that was configured out").
2. x509_cert::ext::AsExtension moved or was renamed.
3. RelativeDistinguishedName and RdnSequence no longer expose their tuple constructors;
   these need to go through the crate's own constructor API.

Leaving this open rather than merging. It needs a human to port crypto.rs.