Implement a mechanism for "free tier" usage of ROFL App

[tjanez]

The idea I discussed with @kostko was that the ROFL App Backend could pay for the app registration as well as for the machine costs and then pass on the admin (ownership) of both the app and machine to the connected wallet's account.

[ptrus]

Rough/minimal backend implementation details:

/api/rofl/build_deploy // accepts manifest and compose as the build endpoint does + also the secrets

1) Submit the rofl create tx to create a new app
2) Build and upload the orc manifest
3) Submit the rofl update tx to set the secrets
4) Submit the roflmarket instance create tx to create the machine
5) Submit the tx to transfer ownership of the machine to the user
6) Submit the tx to transfer ownership of the rofl app to the user
- Handle possible failure scenarios in each step (+ retries?)
- Handle validations, ensure minimal machine resources are selected (with minimal time - 1-2 hours?)
- Ensure this is not abused by bots (captcha + rate limiting)
- Ensure the backend wallet being used is funded

Which means replicating the frontend deployment flow + some extra steps to transfer ownership.

---

This would be the rough implementation if we go down this path. It’s a non-trivial amount of work and I’m not convinced it solves any real problem - especially since deploying an app costs only ~10 ROSE (~30 cents). Realistically, the only thing this would achieve is artificially bumping ROSE app usage stats because someone could create an app just by clicking through the UI without making a single network transaction. I highly doubt this would convert even a single user to the "paid tier".

Personally, I believe the (very low barrier of) 10 ROSE requirement is a good thing, and that low usage might instead be a sign that the existing templates/functionality just aren’t compelling enough.

All that said, did we consider simpler alternatives for start that would be much easier to implement/experiment with?

Alternative 1
Use testnet for the free tier.

In the past I was against this, because as mentioned I believe the 10 ROSE requirement is good, but if we want a "Free tier" this makes by far the most sense to me.

Alternative 2
One-time use codes with enough ROSE to deploy a ROFL app, manually handed out to anyone interested in testing but blocked by not having the ROSE.