create github workflow triggered by manual dispatch that deploys a branch to a cf env

[gobengo]

Motivation:

• ci: remove deploy-dev from .github/workflows/access-api.yml #512 (comment)

[gobengo]

One thing I'm not sure about here is I think any solution that resuses dev may run into issues keeping that cloudflare worker environment's d1 instance up to date (while trying out lots of combinations of git branches over time).
Over time I'd hope cf d1 to find ways of making that easy, but for now its in alpha and doesn't even have 'down' migraitons. https://developers.cloudflare.com/d1/platform/migrations/#plans-for-the-future
(with that said, they could add that feature any day now, and I hope they do so we can use it).

Instead of using a reusable shared cf env like dev, we could make the manual workflow deploy to a cf env derived from the branch name. So then we'd basically have the capability of using github ui to push any branch to a new env, and we can also have a manual workflow to tear it down later. infinity dev envs (aka review apps)!

[vasco-santos]

I would love to see the deploy per branch like we do with SST. We just need to make sure CF APIs allow us to create workers on PR creation and delete workers on PR close/merged to avoid getting CF dashboard full of noise. This is particularly important in CF because for seeing Bucket analytics we need to go through the list of buckets and navigate there