Allow creation of webhooks for project-scoped tokens

[phalbert]

Description

The genesis of this change is documented in this slack thread

What

• Users encounter a 400 error when attempting to create subscriptions (webhooks) due to insufficient permissions to edit the subscription.
• Modify the webhook creation process to include the projectId in the payload.

Why

• The current setup assumes an organisation token when creating webhooks. If a project-scoped token is supplied, the craetion fails

How

• When the user holds a project administrator role, and the PAT is scoped only to that specific project, it is necessary to explicitly define the projectId when creating a webhook.

{
  "publisherId": "tfs",
  "eventType": "git.pullrequest.updated",
  "consumerId": "webHooks",
  "consumerActionId": "httpRequest",
  "consumerInputs": {
    "url": "http://20.246.193.102/ado-port/integration/webhook"
  },
  "publisherInputs": {
    "projectId": "4901a905-d07b-4027-b7cc-577d2b6a0e31"
  }
}

Type of change

Please leave one option from the following and delete the rest:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New Integration (non-breaking change which adds a new integration)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Non-breaking change (fix of existing functionality that will not change current behavior)
• Documentation (added/updated documentation)

Screenshots

Include screenshots from your environment showing how the resources of the integration will look.

API Documentation

Provide links to the API documentation used for this integration.