Please add support for Bearer token in pipelines for the Bitbucket Server Integration Plugin. From JENKINS-75137 I learnt that due to the underlying git client it is not possible to use a bearer token, and you guys removed Secret Text support at all in the recent versions of the plugin. But somehow it's possible to use Bitbucket personal access token (Bearer token) for the configuring the server in the Systems Configuration in Jenkins.

Due to the CAPTCHA implementation in the BitBucket server (several attempts with the bad password lock everyone else with the good password till the CAPTCHA challenge resolved) using the username / password in pipelines becomes a pain in a situations when several jobs are using the same credentials. Each password rotation may lead to a situation that the old password cached somewhere can trigger CAPTCHA challenge. Bearer token doesn't trigger the CAPTCHA, which is extremely helpful.

Please consider doing something with that. Thanks!