[Feature]: PAT and SA token support

Please select the area the issue is related to

Platform API

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Suggested Feature

Anything that interacts with the API Platform programmatically—such as a CI pipeline, deployment script, or integration—currently has to authenticate as a person because the platform has no concept of machine identities. This means employee credentials may be stored in build systems with broader privileges than required, making auditing difficult and creating operational issues when employees leave. It also limits automation-driven features, such as onboarding APIs from Git, which need a dedicated identity to securely authenticate and perform actions without relying on a human user.

Related Issues

No response

Steps to Verify

• Design Document — A detailed design document has been created and reviewed, covering architecture, data flow, and edge cases.
• Design Mail — A design summary email has been sent to relevant stakeholders for awareness and feedback.
• Code Review — All code changes have been peer-reviewed and approved according to the project's review standards.
• Testing Complete — Adequate unit, integration, and/or end-to-end tests have been written and are passing.
• Documentation Review — User-facing and/or developer documentation has been updated to reflect the new feature and reviewed.
• Feature Complete — The feature is fully implemented, all checklist items above are done, and it is ready for release.