[ewiki] include() statements, FEATURE.lst

To get rid of any include() and require() statements (they hurt
the ConfigurationWizard [setup.php] and WebInstaller), I'd propose
something like a feature description database, where single plugins
or multiple fragments would be dependencies for the (more abstract)
"feature" names and descriptions.

The [setup.php] script already has something like that, but I'd
rather like to maintain it in a text file ("FEATURE.lst" or so)
in a rfc822/dpkg-database style format:

  Feature: calendar
  Depends: module/calendar, appearance/title_calendar
  Description: one attached calendar per page

  Feature: blog
  Depends: lib/blog, lib/subpages, calendar
  ...

And so on. Ideally one feature could depend upon another (most simply
would map to one plugin include), and whoever evaluates it would also
know where to search for plugins (so directory names could be omitted).

This was useful to [setup.php] but also to the WebInstaller initially.
Later some online control center plugin could be added to manage all
remaining features for an ewiki setup (= a ConsumerWiki feature). So
such a long FEATURE description database was useful for multiple
purposes, and easier to maintain - but still could be converted easily
into PHP arrays for use with ConfigWiz or WebInstaller.

Other related posts: