[Bug]: branch being deployed is not reported correctly in the Settings, getting "master" instead

### Problem description

The Settings have "master" branch selected by default. So we don't know which branch is being deployed automatically

### Steps to reproduce

1. Deploy a project with Deno Deploy with a branch X different than master
2. Commit on that branch -> it is being deployed automatically -> good
3. Go in the Settings of that project in Deno Deploy -> we see "master" written there in "Production Branch"

### Expected behavior

in the Settings of that project in Deno Deploy -> put X and not "master" as branch deployed in "Production Branch"

### Environment

_No response_

### Possible solution

_No response_

### Additional context

_No response_

Start by reproducing the issue in Deno Deploy: deploy a project from a branch other than master, commit to that branch, and open the project's Settings. The work is done when Production Branch reports the branch actually being deployed rather than master.

Written by the indexing model from the issue text.