Output the deployment ID as part of the action.

This ID already is accessible in the action.

The output will allow subsequent actions to update the Deployment Status of that deployment by calling:

PUT https://.scm.azurewebsites.net/api/deployments/{deploymentId}
{
  "id": "deployment-id",
  "status": 4,                    // Optional, numeric status (e.g., 3 = success, 4 = failed)
  "message": "custom message",     // Optional, a message describing the deployment
  "log_url": "http://yourlog.com", // Optional, a URL for deployment logs
  "active": true                   // Optional, mark this deployment as the active one
}

This endpoint allows updates to a custom message and log_url field. Where we can add the release, a link back to the GitHub runner that invoked the deployment, etc.

Granted, it would be great if we could have this action allow for custom message and set the log_url to the GitHub workflow run. But for now, just outputting the deployment ID is good enough. #74 #442