Updated: Updated share/filelist.md5 for the webserver package rename, so the file consistency check matches the installation again.

Fixed: Fixed the webserver requirement naming a package that no longer exists, by following its rename from qbox-webserver to qbix-webserver and pinning the release that carries the corrected name.

The package was registered under se7enxweb/qbox-webserver, a typo for qbix in
its own composer.json. That has been corrected at the source and Packagist
now serves it as se7enxweb/qbix-webserver; the misspelled name returns 404,
so the requirement added here could no longer be resolved at all.

The pin moves to ~0.0.2 rather than staying at ~0.0.1. Packagist treats a
published version as immutable, so the v0.0.1 tag could not simply be moved
onto the commit carrying the corrected name and be re-read. 0.0.2 is the
release cut for that, and holds the same code.

Still ~0.0.x rather than ~1.0 for the reason it was to begin with: the
package also carries v1.0.0 through v1.3.0, and the binary those ship was
UPX-packed after the phar had been appended as an ELF overlay, which drops
the overlay and leaves an executable that parses its own compressed image as
PHP.

Updated: Updated share/filelist.md5 for the qbox-webserver requirement, so the file consistency check matches the installation again.

Added: Added se7enxweb/qbox-webserver to the project's requirements at 0.0.1, the release carrying the micro binary build fixes.

A pure-PHP web server, so an installation can be served without nginx or
PHP-FPM in front of it.

The constraint is ~0.0.1 rather than ~1.0 on purpose. The package carries
v1.0.0 through v1.3.0 as well, but those predate the build fixes: the binary
they ship was UPX-packed after the phar had been appended as an ELF overlay,
which drops the overlay, so the executable starts and then tries to parse its
own compressed image as PHP. 0.0.1 is the release that stops that, and ~0.0.1
is the constraint that reaches it.

Updated: Updated share/filelist.md5 for the eztags menu label and the matching composer pin, so the file consistency check matches the installation again.

Updated: Updated the pin on eztags to 2.3.5, the release that shortens the top menu entry to "Tags".

The entry read "eZ Tags". It is "Tags" now, which is shorter and does not
carry the old product's branding in an installation that ships as Exponential
6. One line of menu.ini.append.php; no code, schema or behaviour change.

The copy under extension/eztags was brought to the same release, since the
extensions here are working checkouts rather than something composer
installs, and the installation would otherwise keep serving the old label
while the pin named the new one.

Updated: Updated share/filelist.md5 for the bccie menu label and the matching composer pin, so the file consistency check matches the installation again.