Vercel integration - commit association not working after adding SENTRY_RELEASE environemnt variable.

### Environment

SaaS ([https://sentry.io/]())

### Steps to Reproduce

There seems to be a limitation to the our Vercel Integration's commit association feature when renaming releases using environment variable.

1. Setup GIthub integration
2. Setup Vercel integration
3. Configure Vercel integration with a project
4. Create a new Vercel deployment
With the default settings, a new release named after the last commit SHA is created with associated commits.
5. Add a new SENTRY_RELEASE environment variable in (Project Settings -> Environment Variables) to name releases using SemVer
6. Create a new deployment in Vercel

### Expected Result

A new release is created in Sentry following SemVer versioning and commits are associated with it.

### Actual Result

A new release is created with correct SemVer name but with no associated commits.

### Product Area

Settings - Integrations

### Link

*No response*

### DSN

*No response*

### Version

*No response*