Add NEXUS AI to the self-hosting deploy table?

Hi @timothycarambat, before opening a PR (per CONTRIBUTING and your note on #6467): would you be open to listing NEXUS AI in the self-hosting deploy table?

• It deploys the official repository as is. No fork and no template to maintain: it builds docker/Dockerfile from master, serves port 3001, and sets STORAGE_DIR=/app/server/storage, so users always get the current version rather than a pinned image.
• Tested end to end: the image builds, both the server and the collector start, the onboarding UI loads, and /api/ping returns {"online":true}.
• Try it: https://nexusai.run/deploy?repo=https://github.com/Mintplex-Labs/anything-llm&dockerfile=docker/Dockerfile&port=3001&env=STORAGE_DIR=/app/server/storage
• The change would be one column next to Easypanel, in the same reference-link format:

| Easypanel | NEXUS AI |
| --- | --- |
| [![Deploy on Easypanel][easypanel-btn]][easypanel-deploy] | [![Deploy on NEXUS AI][nexusai-btn]][nexusai-deploy] |

Disclosure: I work on NEXUS AI. Totally fine if you would rather wait until there is user demand.