convert libchk and other checkers to version-independent

[Jeff Johnson]

With this summer's GSOC contribution, lsblibchk is now able to be
version-independent, which means all of the checkers have that capability now.

This issue is to track the completion of the conversion to VIP.

There are some minor issues within misc_test itself, such as how a version of a
checker which is intended to validate, say, an LSB 4.0 system, looks - a truly
VIP binary would default to whatever it's built for, is that okay? That is, if
5.0 is the latest LSB release, then libchk and cmdchk will default to checking
against the 5.0 specification. Is that okay?

On a different level, meta-tools will need to know that the pkgs are VIP. Our
lsb-app-checker and lsb-dist-checker tools assume separate repositories for
separate versions... and will perhaps need to know that they /always/ should
specify an LSB version for checks, rather than assuming the default is correct
because we got a package specifically for the LSB version. The repository
generation tools will also need to be aware that the checker pkgs will come
from a common location, not from distinct version-specific places.

Another question to look at is whether there's a split between "production" and
"development" still - the SDK may serve as a model for that, as it currently
does distinguish through some build time tricks.

For the moment, setting this to block app checkers release and distribution
tests release since that covers the areas discussed above. We generally use
the term "Version Independent Packages" in rollup bugs only for between-release
updates, and don't have a VIP-for-5.0 rollup at this time.