OAuth support in trigger-pipeline Bitbucket Pipe

Add support for authentication using OAuth credentials instead of the App password. 

Currently proposed solution is to add two new variables:

• BITBUCKET_CONSUMER_KEY - oauth consumer key
• BITBUCKET_CONSUMER_SECRET - oauth consumer secret

If both App Password and oauth credentials are provided, the pipe should authenticate using oauth.

Why we need this? Mostly because it's not possible to create App Passwords for team accounts to avoid sharing your personal App Password.