bump k8s-openapi features from v1_26 to v1_30

[mscanlon72]

Summary

Bump k8s-openapi features flag from v1_26 to v1_30 to expand Vectors official support of k8s.

Vector configuration

N/A

How did you test this PR?

Requires testing

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

https://github.com/Arnavion/k8s-openapi/releases/tag/v0.22.0

• Related: Vector stops reading logs from EKS with AL2023 based AMIs #24121

Notes

• Please read our Vector contributor resources.
• Do not hesitate to use @vectordotdev/vector to reach out to us regarding this PR.
• Some CI checks run only after we manually approve them.
  • We recommend adding a pre-push hook, please see this template.
  • Alternatively, we recommend running the following locally before pushing to the remote branch:
    • make fmt
    • make check-clippy (if there are failures it's possible some of them can be fixed with make clippy-fix)
    • make test
• After a review is requested, please avoid force pushes to help us review incrementally.
  • Feel free to push as many commits as you want. They will be squashed into one before merging.
  • For example, you can run git merge origin master and git push.
• If this PR introduces changes Vector dependencies (modifies Cargo.lock), please
  run make build-licenses to regenerate the license inventory and commit the changes (if any). More details here.

[thomasqueirozb]

If I'm understanding this correctly, this would mean that anyone using < 1.30 would break. This would need a breaking changelog. Ref: https://docs.rs/crate/k8s-openapi/0.22.0/source/Cargo.toml.orig#46-55