fix: API response of metadata handler on invalid app ID is different from the file get handler

[coderabbitai]

Summary

The metadataHandler in src/Routers/FilesRouter.js returns HTTP 200 with an empty JSON object ({}) when the app ID is invalid (config is missing), while getHandler returns HTTP 403 with "Invalid application ID." for the same condition. This inconsistency can mask configuration errors for callers of the metadata endpoint.

Expected behavior

metadataHandler should return HTTP 403 with an appropriate error message when the config is missing, consistent with getHandler:

       const config = Config.get(req.params.appId);
       if (!config) {
-        res.status(200);
-        res.json({});
+        const error = createSanitizedHttpError(403, 'Invalid application ID.', config);
+        res.status(error.status);
+        res.json({ error: error.message });
         return;
       }

The existing test does not crash on file metadata request with invalid app ID will need to be updated to assert the new 403 response.

Context

Identified during review of #10106 (comment: #10106 (comment)). The inconsistency predates that PR and is intentionally out of scope for it.

Requested by @mtrezza.

[parse-github-assistant]

🚀 Thanks for opening this issue!

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.