Multiple issues and impossible migration to "new" deno deploy

After receiving the email of "Deno Deploy Classic shutting down" I started the migration of multiple OSS projects I had hosted, but I encountered multiple issues with the "new" Deno Deploy that I wanted to come to your attention:

- `deployctl` is being deprecated, so I no longer can build with GitHub Actions and then deploy the files I want the Deno environment to execute (in my case a simple HTTP server script to serve static content)
- the _new_ deployment process requires to specify the build command on Deno Deploy (with a Deno-only env), which makes it difficult for me as I have a Bun project with `bun.lock` file (I ended up "hacking" it downloading the bun executable on the build process to install dependencies and run the build command by using the install path relative to home, see images below)
- after less than a day from the deployment I open my mailbox and saw that I "consumed" all the RAM, apparently I was able to use 10.5GiB/h of RAM for a single project which is a SPA static website (which served 75 requests) (see below images) (maybe you have a little problem with memory leaks?!)

You probably are going to tell me I need to "verify my organization" with a credit card to increase limits but the fun thing is that on the "classic" Deno Deploy i was able to host circa 5 projects + 10 playgrounds and I never got a limit hit.

I know I'm probably not the target of your new Deploy (paying customer) but this is really bad, the "classic" version was perfect for small OSS hosting and now I'm able to have ONE static website without entering my credit card details.