lsbsi changes happening

Sorry to be moving the target when it wasn't
that stable to begin with, but...

We're trying to push various tools forward
into a beta state, and that requires a platform
to test on that implements LSB 2.0 modularization.

The easiest way to set that up seemed to be to
split the lsbsi into lsbsi-core and lsbsi-graphics.

So the checkins flying past now are trying to
make this change.

- lsb_release, which is imported into the lsbsi,
  now knows about modules

- the lsbsi-lsb package, which populates the
  freshly initialized rpm database in the lsbsi,
  now is providing the lsb-core provide

- the lsbsi (phase3) is generating a processor-specific
  /etc/lsb-release file which provides the appropriate
  lsb-core arch-specific, plus lsb-core noarch.

- phase3 is no longer building the xfree package,
  that will now move to be a separate phase. 

There's more work to come...

Question: should the lsbsi addons remain as tarballs,
or should they become rpm packages that install inside
of the lsbsi?  Leaving them as they are (tarballs)
means the rpm database doesn't acquire extra contents,
so I'd probably leave it alone, but it's a question.

Additional modules (just graphics for now) either have
to be an rpm, or have to have a matching mini-rpm
which adds the right provides to the database and
updates the new /etc/lsb-release.d directory.