Add a read endpoint for application settings in the API

[danmt]

Description

Application settings (is_static, is_auto_deploy_enabled, is_force_https_enabled, build flags, GPU options, and so on) can be updated through the API via PATCH /api/v1/applications/{uuid}, but there is no dedicated endpoint to read them back. On the current stable release the application response does not include them at all, so after writing a setting there is no way to confirm the resulting state. On next they are only available embedded in the full application payload.

I am building an external tool that needs to check an application's configuration before deciding whether to trigger a deployment, and right now it has to track that state on its own.

Expected behavior

A read-only endpoint that returns the settings record of a single application:

GET /api/v1/applications/{uuid}/settings

using the same authentication and team scoping as GET /api/v1/applications/{uuid}.

Acceptance criteria

• Returns all fields of the application settings record; internal metadata (ids, timestamps) is not exposed.
• Requires the read token ability; 401 without a token, 404 for unknown applications or applications belonging to another team.
• Documented in the OpenAPI spec.

I have a patch ready and will open a pull request for this.

[danmt]

Closing this one as its not released yet but its part of the next branch