RADAR-6950: Docs | Update Bitbucket Cloud documentation to replace app passwords with API tokens (#1192)

## Description

[RADAR-6950: Docs | Update Bitbucket Cloud documentation to replace app
passwords with API
tokens](https://hashicorp.atlassian.net/browse/RADAR-6950)

DO NOT MERGE until HCP Radar releases v1.45.0 (should ship Thurs/Fri)

App passwords are
[deprecated](https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation)
on Bitbucket, to be replaced with API tokens. Radar support for API
tokens for Bitbucket Cloud will be shipped as part of v1.45.0

<!-- Add a brief description of changes here. Include any other
necessary relevant links -->

<!-- Help your reviewer understand the type of review you need by
selecting the scope and urgency. -->

### Requested review scope:

- [x] Content touched by the PR _only_ (typos, clarifications, tips)
- [ ] Code test (command and code block changes)
- [x] Flow and language near changes (new/rearranged steps)
- [ ] Review everything (rewrites, major changes)

### Review urgency:

- [ ] ASAP (bug fixes, broken content, imminent releases)
- [x] 3 days (small changes, easy reviews)
- [ ] 1 week (default)
- [ ] Best effort (very non-urgent)

<!-- Fill out only the appropriate checklist for your type of feature
(or both if necessary) and delete the other one! -->

## All updates:

<!-- This section is mandatory for all PRs: -->

I have:

- [x] Verified that all status checks have passed
- [ ] Verified that preview environment has successfully deployed
- [x] Verified appropriate `label` applied (`hcp` + `product name`)
- [x] Added all required reviewers (code owners and external)

## Content checklist (optional)

Please do these things before requesting a review. I have:

- [ ] Made any associated code repositories public
- [ ] Added the `hashicorp-education/teamName` to any additional code or
example repos as repo admin
- [ ] Added redirects for any moved or removed pages
- [ ] Spell checked the tutorial(s)
- [ ] Followed the [unified style
guide](https://github.com/hashicorp/web-unified-docs/tree/main/docs/style-guide)
- [ ] Linted code snippets (Details per language
[here](https://github.com/hashicorp/engineering-docs/blob/master/writing/markdown.md#code-blocks))
- [ ] Checked the steps for completeness (no steps are implied or
hidden)
- [ ] Looked at the local or vercel build and checked each new or
changed page for:
  - display on the product curriculum page
  - callout box formatting
  - code block highlighting
  - right-hand navigation
  - next and back buttons
  - URL path

Author: kathytong-hashicorp

content/hcp-docs/content/docs/vault-radar/get-started/add-data-sources/bitbucket.mdx

@@ -23,8 +23,18 @@ Server](#add-bitbucket-server).
 
     ![Workspace Settings](/img/docs/vault-radar/bitbucket-cloud-workspace-settings.png)
 
-- Bitbucket account name
-- App password with the right set of permissions
+- Token creator email address
+- [API token with the right set of scopes](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)
+    - read:account
+    - read:name
+    - read:project:bitbucket
+    - read:pullrequest:bitbucket
+    - read:repository:bitbucket
+    - read:user:bitbucket
+    - read:webhook:bitbucket
+    - read:workspace:bitbucket
+    - write:pullrequest:bitbucket
+    - write:webhook:bitbucket
 
 ## Create a connection with Bitbucket Cloud
 
@@ -34,9 +44,9 @@ Server](#add-bitbucket-server).
 
 1. Enter the workspace in the **Workspace ID** text field.
 
-1. Enter the Bitbucket account name and app password value.
+1. Enter the email address of the Bitbucket Cloud user that created the API token in the **Enter your Bitbucket token creator email** text field.
 
-  ![Configure Bitbucket Cloud](/img/docs/vault-radar/bitbucket-cloud-app-password-permissions.png)
+1. Enter the API token value in the **Enter your Bitbucket API token** text field.
 
 1. Click **Next**.