Issue Summary:
Currently, the Atlassian CLI (ACLI) fails to authenticate when using an Atlassian Service Account. While Service Accounts are designed for automated integrations and use scope-based API tokens, the ACLI appears to only support non-scoped API tokens generated by standard user accounts. When attempting to log in via the CLI with a Service Account email and its corresponding token, the process returns an "Authentication failed" error, even if the Service Account has been granted the necessary application access.

Expected Result:
Users should be able to authenticate the Atlassian CLI using a Service Account email address and a scoped API token, allowing for secure, non-personal automated workflows.

Actual Result:
The command acli jira auth login --site "example.atlassian.net" --email "service-account@serviceaccount.atlassian.com" --token fails with an "Authentication failed" message.

Workaround:
Use a standard Jira user account to generate a non-scoped API token for CLI authentication. This is not ideal for security or automation best practices as it ties the integration to a personal user identity.