added noblogs/themes-misc as a dependency, and removed the corresponding theme patches.
This themes are not on wordpress.org anymore, so they will not be updated from upstream,
and thus we have to keep them in our own repo (but there is no need to separate patches
from upstream).

We might want to consider whether to keep them or remove them in the future.

This commits gets rid of the extra external directory to unpack mu-plugins.
They are instead directly extracted into wp-content/mu-plugins/{name}/, and then the relevant files are copied
(via the drop-in mechanism) to wp-content/mu-plugins/. This leaves spurious directories with undeeded files (readme, composer conf, etc.),
but they should be harmless.

the Drop-in mechanism does not need to specify a file-name, in which case it copies all files (excluding readme.txt and similars). Slightly less stuff to write in this case: plugins which declare themselfs to be mu-plugins will be handled automaticaly, the ones which do not have to be listed twice.

More-privacy-option plugin actually ships with other files (translations), so it should not be considered a mu-plugin, but installed network wide as a regular plugin.

KaTeX is a LaTeX plugin and js library which should be ligher, smaller, faster, but less complete than MathJax (which is what we were using so far). It might be worth to try it as an alternative (I don't think there is heavy usage of Latex on noblogs).

Closes #6

Revert "contrariamente a quanto dicono nella documentazione, si può fare spacchettare tutto nella stessa directory, senza creare una directory wp/ per core"

Si può fare, ma se viene fatto un update di wordpress core poi si perdono tutti i temi/plugin/etc.

Ho cambiato leggermente la struttura delle directory generate, ed ho spiegato tutto dentro README.md

This reverts commit 19f27161.

contrariamente a quanto dicono nella documentazione, si può fare spacchettare tutto nella stessa directory, senza creare una directory wp/ per core

I am still not sure if we want to use Composer to manage the
dependences of r2db, which is only flexihash. It might be easier to
simply add flexihash to the repository of r2db, which we never have
updated in 7+ years. That way we would not need to include the vendor/
folder into the Noblogs production enviroment.

added a theme and a patch as an example

The patch is taken from the git repo noblogs-wp.
It does not apply cleany (yet), since there is an annoying issue with mu-plugins.
They have to be single files, but they are not distributed as single files.
There is a tool which auto-loads them, but I think the mismatch in the directories still causes the patch do not apply nicely.

We have few mu-plugins and we do not update them often, we could think of some solution specific to this problem later.

This is an attempt to re-structre the Wordpress codebase for Noblogs, unsing Composer.