Switch to VirtioFS on Docker Desktop for macOS

[kdambekalns]

With the VirtioFS the direct mounting is fast enough to be used! 🎉

This is needed to use this:

• latest Docker (4.6.0+)
• macOS 12.2+
• enabled VirtioFS (currently experimental)
• remove devkit with the file sync we have in place (or at least make it "switchable")
• mount files directly

To get this to the users, we need to

• adjust the shipped docker compose template
• find a way to cleanly migrate existing .localbeach.docker-compose.yaml files
• restart projects without data loss

Also, do we require a Docker version with (enabled) VvirtioFS support or make it a feature flag?

[kdambekalns]

To use VirtioFS in a Local Beach project, adjust .localbeach.docker-compose.yaml as follows:

• remove the devkit service definition
• remove the application volume definition
• replace the volumes section content on the webserver and php services with just - ./:/application
• in the php service environment section, set BEACH_WAIT_FOR_SYNC=false

[kdambekalns]

Meanwhile VirtioFS is no longer experimental, delegated is a no-op, … this should progress at some point.

Only pitfall: it still seems slower than the old devkit-approach, at least for some. See neos/Neos.NeosIo#473

[kdambekalns]

This has been (partly) addressed by #70, thanks to @ahaeslich!