rework/update/modernize autotool scripts, use automake, standardize file names

Use reasonable AC_CONFIG_SRCDIR in configure.ac

Remove custom INSTALL file; material moved to README, appropriately reworked.

Remove stale files, like lisp/makefile-temp and the various Makefile.in.

Put the still-useful custom macro from aclocal.m4 into
m4/bbdb_with_vm.m4 and remove aclocal.m4 as it is automatically
generated by autotools.

AC_WARN is deprecated in favour of AC_MSG_WARN (thanks autoupdate)

Use an extremely brittle texmf path system: require texmfdir to be
explicitly set.

Give warning rather than error if texmf directory does not exist.

This could be more precise: error if using default, warning only if
option --with-texmf-dir was given.  But when building binaries for
distributions, an error is inappropriate.  And when doing, e.g.,

./configure --with-texmf-dir='$${prefix}/share/texmf'

this test will fail even when the directory *does* exist.  According
to the autotools documentation, only in the actual Makefile is one in
a position to smash these things down into a concrete path!

    (The alternative would be to use the standard autoconf texmf path
    macro.  This used to be called ACLTX_TEXMF_PATH but was renamed to
    AX_LATEX_TEXMF_PATH.  To try it, add AX_LATEX_TEXMF_PATH to
    configure.ac and create the necessary support files:

     m4/ax_latex_texmf_path.m4
     m4/ax_latex_class.m4
     m4/ax_latex_class_report.m4
     m4/ax_latex_package_location.m4
     m4/ax_latex_prog_kpsewhich.m4
     m4/ax_latex_prog_latex.m4
     m4/ax_latex_test.m4

    These can be fetched from the "raw" links on the pre-deletion commits in

     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_texmf_path.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_class.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_class_report.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_package_location.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_prog_kpsewhich.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_prog_latex.m4
     http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_latex_test.m4

    But (a) this fancy texmf path searching doesn't work anyway; (b) the
    support files are removed from the savannah git repo due to a license
    problem.)

fixup! redo
Keep unique master bbdb version number in configure.ac

Other necessary copies of the version number are updated at
configuration time.  This is done by the file lisp/bbdb-version.el
generated from lisp/bbdb-version.el.in, which is then loaded in
bbdb.el.  Due to this, a variety of dependencies related to
bbdb-version.el needed to be added, and some code in configure.ac and
the support m4 macro that attempted to extract the version number from
lisp/bbdb.el could be removed.

NOTE: There is, to my knowledge, *no legal way* to extract the version
number from somewhere else and smoosh it into configure.ac.  The only
way to allow the version number to be changed manually by changing it
in one single place is to have that place be the AC_INIT line in
configure.ac.  Trying to put it in an m4 macro will fail in obscure
ways, like giving distribution tarballs the wrong name.

But if you *did* want to extract it from the lisp sources, knowing
full well that this will not only not work, but will also anger the
gods of autotools who will rain woe upon your most precious
configuration scripts for seven generations of automake, a reasonable
fragment of shell code would be:

${EMACS_PROG} -batch --no-site-file --no-init-file \
       --load lisp/bbdb.el \
       -eval '(princ (if (string-match "^[$]Date[:] \\([0-9/]+\\) [0-9:]+ [$]$" bbdb-version-date) (concat bbdb-version "." (subst-char-in-string ?/ ?. (match-string 1 bbdb-version-date))) bbdb-version))'
update .gitignore
New UUID Generation library for BBDB

In the proposed file format version 7, we want to assign a unique
ID for each bbdb entry. The proposed choice is RFC4122 UUID. I have
found one reasonable and working implementation in pure emacs lisp
by Kan-Ru Chen. However, as I am not qualified to coomment on
the quality of that implementation, I figured it prudent to take
a 'hybridg' approach, namely:

    - If there is a system provided uuid generator (such as uuidgen
      on MacOS X), we will use it by firing a shell comomand

    - If such a utility could not be found, we will use Kan-ru's
      elisp code to get an ID

The present commit merely brings in the library into BBDB while
not referencing it anywere.
File format version 8: auto assign UUID for every record

1. Assign UUID for new records at creation time

2. Provide auto migration from file format v7 to v8 by adding
   bbdb-id UUID field to every record in the database
Updates to README, and a new FAQ section

- Put README in Org mode for easy navigation
- Introduce a FAQ section. with V3 there are so many changes that we
  would like to maintain a set of FAQs for general convenience.