IPFS deployment

### Your use case

Element being the face of a decentralized protocol would be a perfect fit for an official decentralized deployment on IPFS .

Ideally as part of the CI process and normal release cycle of a new version of the web front-end there should be a task that uploads the newly created files to a server that can pin the files on IPFS and publishes the hash in a visible public place(e.g. in the github repo as a badge, as simple link, as a text file part of the releases).

Optional would be for `app.element.io` to use this deployment as the official one [pointing the CNAME to an IPFS gateway](https://developers.cloudflare.com/distributed-web/ipfs-gateway/connecting-website). As an extra side effect, people that host their own home server with a copy of element, now would only have to update some DNS records to point to the latest hash instead of hosting the files manually.

One last pending bit that can be a separate issue is how a `custom.site` can use a separate config for customizability that applies only to that domain. I imagine a well known DNS TXT record could be used for that but its something up for discussion.

### Have you considered any alternatives?

_No response_

### Additional context

_No response_