feat: Implement testing profile with mock vllm in docker compose

[JaredforReal]

What type of PR is this?
feat: Implement testing profile

What this PR does / why we need it:
Implement a MVP of testing profile with mock vllm:

• Added a configurable entrypoint for the router to allow overriding config via CONFIG_FILE(In Docker.extproc and 'scripts/entrypoint.sh`)
• Implemented a mock vLLM service (FastAPI) with a testing profile in Compose ( In tools/mock_vllm)
• Added a testing router config pointing to the mock vLLM(config/config.testing.yaml)

Which issue(s) this PR fixes:
Fixes #189

For reviewer:
This implementation, which has affected numerous files, may be worth discussing. Looking forward to any suggestions.

[github-actions]

👥 vLLM Semantic Team Notification

The following members have been identified for the changed files in this PR and have been automatically assigned:

📁 config

Owners: @rootfs
Files changed:

• config/config.testing.yaml

📁 Root Directory

Owners: @rootfs, @Xunzhuo
Files changed:

• scripts/entrypoint.sh
• Dockerfile.extproc
• docker-compose.yml

📁 tools

Owners: @yuluo-yx, @rootfs, @Xunzhuo
Files changed:

• tools/mock-vllm/Dockerfile
• tools/mock-vllm/README.md
• tools/mock-vllm/app.py
• tools/mock-vllm/requirements.txt

📁 website

Owners: @Xunzhuo
Files changed:

• website/docs/getting-started/docker-quickstart.md

---

🎉 Thanks for your contributions!

This comment was automatically generated based on the OWNER files in the repository.

[netlify]

✅ Deploy Preview for vllm-semantic-router ready!

Name	Link
🔨 Latest commit	19fd13a
🔍 Latest deploy log	https://app.netlify.com/projects/vllm-semantic-router/deploys/68d0a6ed7eb17800080267ce
😎 Deploy Preview	https://deploy-preview-190--vllm-semantic-router.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 project configuration.

[netlify]

✅ Deploy Preview for vllm-semantic-router ready!

Name	Link
🔨 Latest commit	1bd0399
🔍 Latest deploy log	https://app.netlify.com/projects/vllm-semantic-router/deploys/68d28d585c6f6f0008aae424
😎 Deploy Preview	https://deploy-preview-190--vllm-semantic-router.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 project configuration.

[JaredforReal]

@rootfs @Xunzhuo Thanks for your time! This PR is ready for review.

[tao12345666333]

Thank you, left one comment.

[rootfs]

can you move the dockerfile optimization to another PR?

[rootfs]

@JaredforReal lgtm, can you move the dockerfile optimization out this PR? we can review them in the followup one.

[yuluo-yx]

Thanks for your contribution.

There are currently 4 items related to docker. I'm wondering if we should move them to the "tools/deploy" or "tools/docker" directories? This would make the project root directory cleaner and neater.

[JaredforReal]

@rootfs @yuluo-yx Thanks for your advice! I will work on them ASAP

[JaredforReal]

Thanks for your contribution.

There are currently 4 items related to docker. I'm wondering if we should move them to the "tools/deploy" or "tools/docker" directories? This would make the project root directory cleaner and neater.

@yuluo-yx Got u, we already have a deploy/kubernetes in the root dir, which I haven't read and tried. I will try to wrap files related to Docker (including scripts/entrypoint.sh) in a tools/docker folder and make them more graceful and easier to understand. Thanks!!

[JaredforReal]

@yuluo-yx Got u, we already have a deploy/kubernetes in the root dir, which I haven't read and tried. I will try to wrap files related to Docker (including scripts/entrypoint.sh) in a tools/docker folder and make them more graceful and easier to understand. Thanks!!

@yuluo-yx Thanks for your advice! I have tried to move docker files to tools/docker, and write another docker.mk for docker operations, like up, down, and testing to make it easier to use.
However, these changes affect the GitHub CI workflow, which makes this PR too complicated. I would like to do this in another PR with community's approval :)
So, I'm gonna leave the usage for now, and improve it later, Thanks again