V1 API appears to return 200 for pages that should 404

### Current Behavior

The FlowForge V1 api appears to always return 200 with an empty response, even for an endpoint that does not exist


### Expected Behavior

Should throw a 404

### Steps To Reproduce

Make a post request to any non-existant path

### Environment

_No response_

Start by reproducing a POST request to a nonexistent V1 API path and inspect the V1 API routing or entry point responsible for the response. Done means nonexistent paths return HTTP 404 instead of HTTP 200 with an empty response.

Written by the indexing model from the issue text.