[Rust-Axum][Breaking Changes] Extracting Claims in Cookie/Header

[linxGnu]

This PR helps handling Authentication via API key (in Header and in Cookie). Extracted Claims are now sent to all Operations

Integration tests passed:

mvn clean && ./bin/generate-samples.sh bin/configs/manual/rust-axum-* && mvn integration-test -f samples/server/petstore/rust-axum/pom.xml

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  
  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[linxGnu]

User Impl this trait to extract Claims (e.g: JWT) from Header/Cookie.

[linxGnu]

Extracted Claims (in previous step) is injected into Operation. User then can do whatever he/she wants with the Claims (e.g: get AccountID from the Claims)

[linxGnu]

Kindly ping @wing328 to review

[linxGnu]

Bug fix here. We must use keyParamName instead of transforming

[wing328]

thanks for the PR. let's give it a try

if users need the old behavior with a valid use case, we will come up with a way for that.

[linxGnu]

Thank you for reviewing @wing328