[WIP] Groundwork to support OpenAI API endpoints that vLLM supports

[kfswain]

This PR sets up envoy to share request path attributes with EPP, and creates a set of maps to determine which routes we allow, and which are just passthrough.

Optionally, we can make the decision that EPP should do no route enforcement, and then we only map the RoutableEndpoints and assume any other route is just passthrough.

The route list was made from an intersection of the endpoints in:

• https://github.com/vllm-project/vllm/blob/main/vllm/entrypoints/openai/api_server.py
  &&
• https://platform.openai.com/docs/api-reference/introduction

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kfswain

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [kfswain]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	d604a20
🔍 Latest deploy log	https://app.netlify.com/sites/gateway-api-inference-extension/deploys/67d9b5e6b4512300088ab14c
😎 Deploy Preview	https://deploy-preview-526--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[hzxuzhonghu]

For these passthrough api sendpoints, users should setup policies to tell envoy not send the request to epp at all. It's better to shortcircuit in envoy.

[ahg-g]

where is this used?

[kfswain]

It's not currently.

I just threw this together to have a hard example of what I was thinking.

I should ahve had a WIP prefix on this PR, I do now. Apologies