ops: define cleanup script for cloudflare deployments

[vladjerca]

This pull request, a digital cleanup crew armed with a rusty wrench and a cryptic script, descends upon the projects/client directory, leaving a trail of updated configurations and purged Cloudflare deployments in its wake. Observe, with a mix of curiosity and apprehension, the meticulous adjustments to Deno paths, the conjuring of a cleanup script, and the subtle yet impactful modifications to the package.json file.

Configuration updates (or, "The Pathfinding Expedition, Part III"):

• The .vscode/settings.json file, a treasure map of developer preferences, undergoes a cartographic correction, its deno.disablePaths setting now pointing towards the projects/client/src directory, like a compass needle guiding developers towards the true source of code.

New Cloudflare cleanup script (or, "The Digital Grim Reaper"):

• The cleanup-cloudflare.ts script materializes from the depths of the .scripts directory, a digital grim reaper tasked with purging outdated Cloudflare deployments. This automated executioner, armed with functions for fetching and deleting deployments, promises to maintain order in the server's attic, ensuring that only the most recent 15 deployments remain, like trophies on a digital mantlepiece.

Package updates (or, "The Script Summoner"):

• The package.json file, a registry of project commands, welcomes a new addition: the cloudflare:cleanup script, an incantation for summoning the Cloudflare cleanup script. This new command, a testament to our desire for automation and efficiency, empowers developers to unleash the digital grim reaper with a single command, purging outdated deployments and maintaining a clean and organized server environment.

These changes, a testament to our ongoing struggle against digital clutter and our relentless pursuit of code hygiene, collectively enhance the project's maintainability and streamline the management of Cloudflare deployments. The updated Deno paths configuration ensures that developers can navigate the codebase with ease, while the new cleanup script automates the tedious task of purging outdated deployments. The result is a cleaner, more organized project, where outdated deployments are swiftly dispatched to the digital graveyard, and the server remains a haven of efficiency and order.

300 deployments deleted