Client: fix paths for non-transarc locations

* Fix the systemd unit so it uses the system paths instead of transarc
paths.
* Include the correct paths in the files section
* Define the cache directory in the client package
* Mark the CellServDB files as config files
Add Compatibility subpackages, transarc server and client subpackages

* Re-add the -compat subpackage from upstream
* Create two -transarc packages
** Client: contains /usr/vice/ symlinks
** Server: contains /usr/afs/ symlinks
Bump up to version 1.6.10, include volscan
Move kaserver man pages into server rpm
openafs-kmod: import openafs.spec from upstream project
openafs-kmod: Only build kernel module

I've removed everything related to the openafs project except for
building the kernel module.

Added to this is a new executable, find-installed-kversion.sh, which
uses the installed kernel headers to define the kversion, so the build
process no longer uses the output of `uname -r` or a --define
parameter to the rpmbuild command.  Instead, it parses
LINUX_VERSION_CODE and RHEL_RELEASE defined in <linux/version.h> and
builds the kversion from this.

Also, we're using the Red Hat kmodtool script instead of the OpenAFS
one.  It looks like this might make it easier to build dependencies
against kernel symbols instead of particular kernel releases.
find-installed-kversion.sh: make sure to output a define command
openafs-kmod.spec: add 'kernel' as a BuildRequires

The Red Hat rpmbuild automatic dependency generator uses the kernel's
symbols to add kernel symbol dependencies to the package.  For
example, if the kernel module uses vprintk(), it might use add this as
a dependency to the kmod package:

kernel(vprintk) = 0xbf8ba54a

To get access to the kernel symbols, the rpmbuild automatic dependency
generator needs the 'kernel' package installed.
Bumped version to 1.6.10