core: tools: nginx: Add a 404 if extension is not registered

[patrickelectric]

Fix #3904

Summary by Sourcery

Bug Fixes:

• Ensure unknown /extensionv2/ routes return a 404 error rather than being handled by the single-page application.

[sourcery-ai]

Hey - I've left some high level feedback:

• The error_page 404 = @extension_not_found; directive in the /extensionv2/ location is never used because the return 404; immediately exits; either remove the error_page/named location or move the JSON response directly into the main location block.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `error_page 404 = @extension_not_found;` directive in the `/extensionv2/` location is never used because the `return 404;` immediately exits; either remove the `error_page`/named location or move the JSON response directly into the main location block.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[patrickelectric]

Tested and working:

[Williangalvani]

nice!

[rafaellehmkuhl]

@patrickelectric I believe this PR is a good defensive measure, but it doesn't fulfill the needs of #3904?

[rafaellehmkuhl]

@patrickelectric I believe this PR is a good defensive measure, but it doesn't fulfill the needs of #3904?

Just tested and it actually does.