Add fib-related configuration variables to let some tests run.

This is to allow a bunch of tests that were marked as skipped to actually
run on the various configurations we support.

Requested by asomers.
Reenable the build of lib32.

Remove the WITHOUT_LIB32 override hack that was originally required to let
the tests build.  The root cause behind the problem was fixed in r261132
for HEAD and in r261849 for stable/10.
Allow sys/netinet/fibs_test:arpresolve_checks_interface_fib to run.

Do this by installing nmap and socat on the virtual machines (and by
adding support to autotest to install arbitrary packages).
Add missing svn properties.

Originally missed due to the lack of an extension in the filename.
Turn setup into an shtk-based script.

This means that "pkg install shtk" must be run first on the host by hand,
but that's easy enough to do.  Added a check to the Makefile to ensure
that shtk is present.

The reason for doing this is that I want to add extra logic to this script,
and that logic will be much easier to implement with shtk.
Make setup.sh allow a controlled deployment of specific autotest versions.

With this change, setup.sh will fetch a separate copy of autotest (and its
dependencies!) based on a revision specification in a per-host
configuration file.  This separate copy is the one used on the worker node
to run the tests.

Additionally, setup.sh will register itself as a cron job to maintain the
autotest code and all configuration files up-to-date.

The goal of this change is to permit having one of the kyua[123] workers
as a canary of configuration changes while the others remain stable.  This
is much necessary as I've been known to routinely break the nodes when I
manually push to them untested changes.
Update documentation according to yesterday's changes.

I missed committing this file because I ran "svn commit" from the wrong
subdirectory.  Yes, yes, git user here.
Add nginx configuration.

Set up nginx in the same way in all cluster machines and install the same
static files.

While doing this, remove a spurious comment that sneaked in in the last
change that prevented autotest_node from being started.
Fix shtk presence validation by actually aborting the build when missing.
Add configuration files for kyua3.

These files are a verbatim copy of the files for kyua1.  This is because
I intend to replace kyua1 with kyua3 and leave kyua1 as the canary machine.
Determine whether to use svnlite or svn.

Cluster machines are configured with WITH_SVN=yes, so let's not assume
that the binary is called svnlite.
Fix nginx setup as part of the "all" target.

That's it.  "./setup all" on a fresh host now works properly to create a
full clone of an autotest node.
Push new configs to kyua3.
Make sure the cron job can find all the binaries that it needs.

Set the PATH to include /usr/local so that we can execute svn and git
properly.  Oh, and also make sure to install git on the host.
Turn kyua1 into a canary host for autotest.

kyua1 will now run bleeding-edge autotest+shtk, will only run tests for
amd64 HEAD and will run release builds with NO_CLEAN=yes set for faster
turnaround.

All changes to autotest should go through this machine first and only be
pushed to the other workers when they are confirmed to be working for at
least one full release build.

The previous responsibilities of kyua1 have been migrated to kyua3 and
the index page has been updated accordingly.
kyua1 is the one supposed to use NO_CLEAN=yes, not the others.
Push clean builds to kyua[23].
Fix crontab patching by not killing everything else that is supposed to exist!
Push crontab patching fixes to kyua[23].

Verified working on kyua1.
Skip host.conf when auto-detecting config files for iterate.sh.

This is a hack, but is the easiest to get out of a little problem in the
configuration...