Add IPFS for seamless distributed file serving

**is your feature request related to a problem? Please describe.**
At the ChaosCommunicationCongress people seem to be frustrated by fileserver with insuffcient bandwidth and are asking for distributed protocols.

**Describe the idea / solution you'd like**
I'd wish that files optionally can be distributed via IPFS. For simplicity let's assume that there is a Kubo instance on the server ([see](https://docs.ipfs.tech/quickstart/pin-cli/)), it would then be possible to add a header while serving files ([see](https://docs.ipfs.tech/how-to/companion-x-ipfs-path-header/)). That would allow for seamless integration of a distributed system without breaking user expierience.

**Describe any alternatives you've considered**
It would also be nice if for each file a torrent-file could be generated. that would also require an additional server/protocol and would break the user experience since we would leave the browser.

**Additional context**
I have not yet tested the idea yet. If helpful we could test IPFS adoption together at 40C3.

The issue suggests integrating IPFS for file serving, likely by adding a header while serving files. Start by examining the file serving logic in the codebase to understand where HTTP headers are added. Look for a Kubo instance setup as mentioned. Check if there are existing integrations with distributed protocols. 'Done' would mean files can be optionally served with IPFS headers without breaking the user experience.

Written by the indexing model from the issue text.