feat(credentials): add Atlassian service account credentials

[TheodoreSpeaks]

Summary

• Add atlassian-service-account credential type backed by a scoped Atlassian API token, surfaced in Jira and Confluence credential dropdowns alongside OAuth
• Validate via the gateway flow: _edge/tenant_info (unauth) to discover cloudId, then api.atlassian.com/ex/jira/{cloudId}/rest/api/3/myself with Bearer to verify the token works
• Plumb cloudId from the token route through tools and selectors so blocks skip the runtime accessible-resources call (which 401s for scoped service-account tokens)
• Extract reusable ServiceAccountForm (Google JSON-key paste/upload) and new AtlassianServiceAccountForm (token + domain) from integrations-manager; map typed server error codes to friendly inline copy
• Lift code from error response bodies into ApiClientError.code so any form/hook can switch on it without re-parsing

Type of Change

• New feature

Testing

Tested manually end-to-end (credential creation, project picker, runtime block call). bun run lint and bun run check:api-validation:strict both pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29606901	Triggered	Generic High Entropy Secret	a54dcbe	apps/sim/providers/utils.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e017f19. Configure here.}

[cursor]

Unreachable duplicate_display_name error code mapping is dead code

Low Severity

The duplicate_display_name key in ERROR_MESSAGES can never be matched. The server's AtlassianValidationError handler in the credentials route returns { code: error.code } where error.code is typed as AtlassianValidationCode, which only includes invalid_credentials, site_not_found, and atlassian_unavailable. The existing duplicate-credential detection paths (findExistingCredentialBySource returning 409, or the 23505 DB constraint handler) return responses without a code field, so codeFromErrorBody yields undefined on the client. Users who hit a duplicate see the generic fallback message instead of the intended friendly copy.

 

^{Reviewed by Cursor Bugbot for commit e017f19. Configure here.}