[Bug]: Cannot Promote Deployment to Production Due to databaseBindingMismatch Error

### Problem description

Since recently, I can no longer promote deployments to production via [dash.deno.com](https://dash.deno.com/). Every time I try, I receive the following error message:
```json
{"name":"ApiError","status":400,"code":"databaseBindingMismatch","traceId":"****","retryAfterSec":null,"message":"The requested deployment is binded to a different set of databases than the current production deployment."}
```
I can provide the `traceId` if it helps and would be save to share.

I initially deployed using deployctl and later connected my GitHub repository to Deno Deploy. Since then, promoting deployments to production no longer works.

This issue seems similar to [denoland/deploy_feedback#808](https://github.com/denoland/deploy_feedback/issues/808), but I have not used Deno KV at all in my project.


### Steps to reproduce

I'm not too sure about it, but that seems like the way it went:

1. Deploy a project using deployctl.
2. Connect the project to a GitHub repository.
3. Attempt to promote a deployment to production via [dash.deno.com](https://dash.deno.com/).

### Expected behavior

The deployment should be promoted to production without issues.
In addition, a more helpful error message would be practical, I can't understand what the error message is supposed to tell me at all

### Environment

- https://dash.deno.com/
- deno 2.1.10 (stable, release, x86_64-unknown-linux-gnu)
- v8 13.0.245.12-rusty
- typescript 5.6.2

### Possible solution

_No response_

### Additional context

- Deno Deploy dashboard
- Initially deployed via deployctl, later connected GitHub
- No usage of Deno KV in the project