Recommend using a service account for BitBucket (#5302)

## What are you changing in this pull request and why?

Making sure people understand to use a service account with BitBucket.
Some follow up questions:

- Should all git providers use a service account?
 
## Checklist
<!--
Uncomment when publishing docs for a prerelease version of dbt:
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/vercel.json`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages

website/docs/docs/cloud/git/import-a-project-by-git-url.md

@@ -56,7 +56,13 @@ If you use GitLab, you can import your repo directly using [dbt Cloud's GitLab A
 
 ## BitBucket
 
-- To add a deploy key to a BitBucket account, navigate to **SSH keys** tab in the Personal Settings page of your BitBucket account.
+Use a deploy key to import your BitBucket repository into dbt Cloud. To preserve account security, use a service account to add the BitBucket deploy key and maintain the connection between your BitBucket repository and dbt Cloud. 
+
+BitBucket links every repository commit and other Git actions (such as opening a pull request) to the email associated with the user's Bitbucket account.
+
+To add a deploy key to a BitBucket account:
+
+- Navigate to **SSH keys** tab in the Personal Settings page of your BitBucket account.
 - Next, click the **Add key** button and paste in the deploy key generated by dbt Cloud for your repository. 
 - After saving this SSH key, dbt Cloud will be able to read and write files in your BitBucket repository.