Instructions on how to configure an API Token with Scopes for Jira Authentication

**Is your feature request related to a problem? Please describe.**
When authenticating the extension with Jira Cloud sites where the user's authentication method is SSO using Google, the extension asks for an API token.

When creating an API Token in the Atlassian interface, there is a warning with the following details:
```
API tokens without scopes are being deprecated
We encourage creating the more secure API tokens with scopes whenever possible.
```

It's not clear what Scopes should be applicable to an API Token to use with the AtlasCode extension for authenticating with Jira.

**Describe the solution you'd like**
- Provide details in the extension of what API Token Scopes are needed for AtlasCode's Jira connection.
- Have a preconfigured scopes option for the extension visible in the API Tokens interface.

**Describe alternatives you've considered**
- Change the AtlasCode Jira authentication to use OAuth similar to the AtlasCode BitBucket authentication.

**Additional context**

## Jira Authentication and attempting to create an API Token with Scopes
---
---

---
---
---
## Outcome of Bitbucket authentication, not requiring an API Token

The issue names no files, tests, or entry points. Start by locating the Jira authentication flow and reviewing the Atlassian scoped-token requirements; done means the required scopes and setup instructions are clearly provided, with any requested extension or interface changes defined.

Written by the indexing model from the issue text.