#14712: New files from Fly.io Launch

<!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR replaces the existing OpenClaw Fly.io deployment configuration (`fly.toml`) with a generated Fly Launch template. In doing so, it changes the app name, switches the service port to 8080, and removes the repository’s documented Fly settings (Dockerfile build, environment variables, explicit gateway process command, and persistent `/data` volume mount). The current repo deployment guide (`docs/install/fly.md`) and the private template (`fly.private.toml`) assume a gateway process bound to LAN on port 3000 with state persisted under `/data`; without those settings, Fly health checks/ingress and persistence won’t match how OpenClaw is intended to run. <h3>Confidence Score: 1/5</h3> - Not safe to merge: the Fly.io config will likely break deployments and persistence. - The only changed file is fly.toml, and it no longer matches the repo’s documented Fly deployment requirements (port/process/env/mount), plus it contains conflicting VM memory settings. These are high-impact configuration errors for anyone deploying via Fly. - fly.toml <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->