Github Integration Improvements (Additional Metadata)

### Required Terms

- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)

### What service(s) is this request for?

Heroku / Github Integration

### Tell us about what you're trying to solve. What challenges are you facing?

It would be great if Heroku would pass through some deployment metadata with the Github integration when the deployment resource is created, especially the Heroku release/version number.

Metadata like that can be included on the `payload` key that's outlined in the GitHub API documentation [here](https://docs.github.com/en/rest/deployments/deployments?apiVersion=2022-11-28#create-a-deployment)

The main use case for this is in private spaces multiple deployment_status multiple web-hooks are sent due to the way the release phase lifecycle is managed. Add-ons like Activity 2 Go in the Heroku elements marketplace are basically useless and create a lot of duplicate notifications/noise as a result.

Passing along the Heroku version metadata would allow GitHub Actions to be setup to reliably fetch the release to retrieve information related to it for surfacing in notifications elsewhere.

Additionally having access to the previous released versions sha/commit either through the deployment creation, would be amazing, or even passing along a generated `Compare Diff` URL that you generate in the Heroku interface it self: