Cargo: 0.17.0 -> 0.18.0, update cc, data-encoding, oid-registry

[cpu]

Cargo: 0.17.0 -> 0.18.0

This commit updates the version number to reflect that a breaking change was made in master. This in turn fixes the cargo-semver-checks-action finding in CI.

In https://github.com/rusticata/x509-parser/commit/ce50cdb38a742dbe85a9a2f5fd79ad4caf2bf42a a new variant (GeneralName:Invalid) was added to GeneralName, and since that enum isn't marked non_exhaustive, this is a semver incompatible change that necessitates increasing the Cargo version.

This was correctly flagged by the CI cargo-semver-checks action, but since the commit was pushed directly to master it seems to have been overlooked.

@chifflier would you be open to switching to a pull request workflow? I would be available to try and review incoming PRs if you're interested in that, but even if you merge them yourself without review I think it's worthwhile as a way to verify CI passes pre-merge.

Cargo: update cc, data-encoding, oid-registry

Updates 3 packages to latest compatible versions: Updating cc v1.2.11 -> v1.2.13 Updating data-encoding v2.7.0 -> v2.8.0 Updating oid-registry v0.8.0 -> v0.8.1

Notably the oid-registry update requires replacing usages of the deprecated typo'd OID_X509_EXT_INHIBITANT_ANY_POLICY OID with OID_X509_EXT_INHIBIT_ANY_POLICY.

Replaces https://github.com/rusticata/x509-parser/pull/181, #182 where I noticed the builds failling.