Updated: Version bump on ezupdate package to 1.0.2

Updated: Updated the explayouts constraint to 1.2.1, so installs are guaranteed the nexus node map fix that keeps block links pointing at the right content.

Fixed: Fixed every content class the base data seeds installing with a blank name, by not copying an eng-GB name that does not exist.

The CreateSites step converts a base installation seeded in eng-GB to the
chosen primary language. It did that by copying the eng-GB entry of each name
list onto the primary language:

  $classAttribute->NameList->setName(
      $classAttribute->NameList->name( 'eng-GB' ), $primaryLanguageLocaleCode );

Our base data is seeded in eng-US, so there is no eng-GB entry, name() returns
an empty string, and that empty string was written over the real name.
eZContentClass::store() then serialised it as

  a:2:{s:6:"eng-US";s:0:"";s:16:"always-available";s:6:"eng-US";}

which is byte for byte what eZContentClassNameList::initDefault() produces, so
the result looked like a name list that had never been initialised.

The loop covers classes and their attributes, which is why both levels were
affected, and it only sees classes that exist at that point in the wizard -
the ten the base data seeds: folder, article, user, user_group, image, file,
link, comment, common_ini_settings and template_look. On this installation that
was 10 class names and 50 attribute names, blank in the class list, the create
here menus and anywhere else a class or attribute label is printed.

The ezcontentclass_name rows escaped for two reasons, both in the same block:
the UPDATE above it only rewrites rows whose locale is eng-GB, which is a no-op
when the data is already seeded in the primary language, and
setHasDirtyData( false ) then deliberately skips rewriting them. That is why
the names survived in that table while the serialized column was emptied, and
why the two disagreed.

The name is now only carried across when there is one to carry.
setAlwaysAvailableLanguage() and removeName( 'eng-GB' ) still run unconditionally,
so a genuine eng-GB installation converts exactly as before; this only declines
to write when there is nothing to write.

Verified by replaying the conversion against real classes, old logic against
new, in memory: the old path reproduces the empty serialisation exactly and the
new path preserves Folder, Article, User group and the folder name attribute.
See ai/bin/one/test_class_name_language_conversion.php.

Updated: Updated three explayouts constraints that could never reach their latest release.

A tilde constraint on a three part version does not cross a minor, so
~1.0.0 means >=1.0.0 <1.1.0. explayouts has since released 1.1.0, 1.1.1 and
1.2.0, and explayouts-ui and explayouts-ui-api have released 1.1.0, none of
which the constraints allowed. The pins were raised to the current minor:

  se7enxweb/explayouts          ~1.0.0 -> ~1.2.0
  se7enxweb/explayouts-ui       ~1.0.0 -> ~1.1.0
  se7enxweb/explayouts-ui-api   ~1.0.0 -> ~1.1.0

This class of staleness is invisible to composer outdated, which reports only
what is installable within the current constraints - so a constraint that has
fallen behind its package satisfies itself and is never mentioned. The three
were found by querying Packagist for the newest stable release of each of the
57 se7enxweb packages and testing it against the declared constraint;
ai/bin/one/check_composer_constraints.py does this and now reports none
excluded. The other 54 were already correct.

Constraints only. composer.lock is untouched: thirteen packages are locked
behind a release their constraint already permits, and refreshing that lock is
a separate decision, not least because most of these extensions are live git
checkouts rather than composer installs.

Added: Added the finish time and elapsed duration to the kickstarter setup summary, so two runs of the same kickstart.ini can be told apart in the console output.

Updated: Updated the sevenx-themes-media constraint to 1.5.1, so installs are guaranteed the meta description and image alt text fixes rather than merely allowed them.

Updated: Updated the sevenx-themes-media constraint to the 1.5.0 series, so installs pick up the working favicons and the removal of node ids and eng-GB the theme used to ship.