Provide the example found here https://docs.konghq.com/gateway/latest/configure/auth/allowing-multiple-authentication-methods/ translated to an example under the KIC guides.

### Where is the problem?

https://docs.konghq.com/kubernetes-ingress-controller/latest/

### What happened?

We found the page [multi-auth-methods](https://docs.konghq.com/gateway/latest/configure/auth/allowing-multiple-authentication-methods/) which describes this example use case using the Admin API, looking for this as an example (as a guide ) under the KIC documentation but could not find it.

### What did you expect to happen?

It would be good to see ( where applicable ) examples like the one given expressed as a guide under KIC. So in this case the Configure section under Kong Gateway expressed as a set of guides under KIC that way there is a direct comparison between how this is done using the Admin API and decoratively under KIC.

This would also improve consistency of examples within the docs.

### Code of Conduct and Community Expectations

- [X] I agree to follow this project's Code of Conduct
- [X] I agree to abide by the Community Expectations

Compare the Kong Gateway multi-auth-methods example at https://docs.konghq.com/gateway/latest/configure/auth/allowing-multiple-authentication-methods/ with the KIC documentation entry point at https://docs.konghq.com/kubernetes-ingress-controller/latest/. Identify the appropriate KIC guide location and express the same use case there, preserving a clear comparison between Admin API and declarative Kubernetes configuration. Done means the translated example is published in the relevant KIC guides and matches existing documentation conventions.

Written by the indexing model from the issue text.