When a workspace SSH key is used to push to a repository, a warning is displayed that the account does not have an email address

Issue Summary

When a workspace SSH key is used to push to a repository, a warning is displayed in the push output indicating that the account does not have an email address associated with it.

Steps to Reproduce

1. Generate an SSH key pair
2. Add the public SSH key to a workspace's SSH keys
3. Modify your ~/.ssh/config file to use this specific SSH key for bitbucket.org
4. Clone a repository of this workspace via SSH
5. Make a change in your clone and push it to the repo

Expected Results

No warning should be displayed in the output of the push command.

If we'd like to make users aware of the fact that they're using a workspace SSH key, we could perhaps show a message that the SSH key used is associated with a workspace instead of an account.

However, it would also be useful to provide an option to disable such console messages for workspaces, similar to the "Enable console messages" option for accounts.

Actual Results

The following is displayed in the output of the push command:

remote: Warning!
remote: Your account does not have an email address associated with it
remote: Please set one by visiting https://bitbucket.org/account/user/WORKSPACE_UUID/email/

A workspace cannot have an email address associated with it, therefore this message is unnecessary and it can also be confusing for users.

Workaround

If a workspace SSH key is used, there is no workaround for this behavior. A workaround will be added here when available.

The SSH key can be added to the Bitbucket account of a user with access to this workspace (instead of the workspace SSH keys). In this case, the warning is not displayed.