If a user registered a Bitbucket Cloud credential with Blue Ocean and then later changes their Bitbucket / Atlassian password, they receive an opaque error message with no obvious way to fix it.

Repro Steps

1. Click "New Pipeline" from Blue Ocean dashboard
2. Click "Bitbucket Cloud"
3. Enter a valid user name and password
4. Note: credential is saved successfully and user is prompted to choose a team.
5. Open a new tab and navigate to Bitbucket or Atlassian account manager and change the password.
6. Click "Bitbucket Cloud" again (to relaunch the flow)

Expected Behavior

• User should see the credential step with an error message indicating the stored credential is no longer valid.

Actual Behavior

• User received "Unauthorized" error message

Workaround

• User must enter classic, open their credentials listing and delete their "bitbucket-cloud" credential, then relaunch the creation flow

Notes

• I believe this also affects Bitbucket Server.
• I don't believe this is a regression but rather a defect in the original implementation.
• This kind of "credential revalidating" behavior is implemented in GitHub and GitHub Enterprise. AbstractBitbucketScm.getState just needs to add some logic to validate the existing credential again.