Expose workspace in branch permissions

When using the client credentials grant flow to generate OAuth credentials, Bitbucket associates the credential owner (in shared workspaces, the workspace itself) as the authenticated user for permission reasons.

This causes problems mainly when using branch permissions in Bitbucket, as the workspace is not exposed to the branch permissions, so it's impossible to perform requests with those credentials if branch permissions are enabled.

This feature request is to expose the workspace itself in the branch permissions, so that OAuth credentials that are associated with the workspace are allowed through the branch permission if the workspace owner so desires.

The fix for this would be similar to what's being requested on https://jira.atlassian.com/browse/BCLOUD-19136.