Add support for Application Consents API

[crowdin-bot]

The Crowdin API introduces Application Consent Decisions methods for managing consents granted or denied to applications. Note: these endpoints are available on crowdin.com only (not in Crowdin Enterprise).

• List Application Consents — GET /applications/consents (api.applications.consents.getMany). Query: identifier (string, optional), orderBy (id, createdAt), limit/offset.
• Add Application Consent — POST /applications/consents (api.applications.consents.post). Request: identifier (string, required), installedBy (integer, required), status (granted or denied, required), scopes (array of strings, optional). Returns 409 on duplicate.
• Edit Application Consent — PATCH /applications/consents/{consentId} (api.applications.consents.patch). JSON Patch with op: replace and paths /status, /scopes.
• Delete Application Consent — DELETE /applications/consents/{consentId} (api.applications.consents.delete).

The response model includes: id, installedBy (nullable object with id, username, fullName, avatarUrl), identifier, name (nullable), status, scopes, createdAt, updatedAt.

Client libraries should add these methods to their Applications API support.

References:

• List Application Consents
• Add Application Consent
• Edit Application Consent
• Delete Application Consent