Project detail page should probably show project name somewhere even though custom domain is set

### What problem are you trying to solve?

If a custom domain is configured to a project, that custom domain is shown at the top in the project detail page:


However if this project is supposed to be deployed through GitHub Actions, we need to specify a project name, not a domain. With the current UI, it may be a little bit hard to tell what the project name is, unless you are familiar with Deno Deploy or you happen to get to "Settings" tab where you can find `Project Name` section that indicates what your project name is.


### Describe the solution you'd like

Place `project name: your-project-name` (possibly as well as `project ID: xxxxxxx`) next to the custom domain name at the top, to help users easily understand what the project name is.

As a reference, this is a screenshot from subhosting top page, where it clearly shows organization ID.

### Describe alternatives you've considered

Maybe we could support custom domain as an identifier of a project in `deployctl` action? In other words, we could maybe get something like this working:

```yaml
- name: Deploy to Deno Deploy
uses: denoland/deployctl@v1
with:
project: my-project.example.com
entrypoint: main.ts
```

But this would require more work than my first suggestion.

### Documentation, Adoption, Migration Strategy

_No response_

Start at the project detail page and compare its header with the Settings tab's Project Name section. Confirm how the project name, and optionally the project ID, is exposed, then check the GitHub Actions/deployctl workflow to ensure the displayed identifier matches what deployments require. Done means the project name is visible beside the custom domain.

Written by the indexing model from the issue text.