Use dgrid event and set query instead of manual update

While I'm here remove unused modules.

Ticket:	#6300
Show only known volumes in the Periodic Snapshot Task Form

Ticket:	#6335
Map groups when created and unmap when deleted
Do not list snapshots in the root pool

Ticket:	#6335
A whole slew of changes, almost all entirely in terms of additions.

Slightly edited version of the email I sent to William describing
what I'd do:

DownloadUpdate(train, directory)
	Download, if necessary, the LATEST update for train; download
	delta packages if possible.  Checks to see if the existing content
	is the right version.  In addition to the current caching code, it
	will also stash the current sequence when it downloads; this will
	allow it to determine if a reboot into a different boot environment
	has happened.  This will remove the existing content if it decides
	it has to redownload for any reason.

PendingUpdates(directory)
	Return a list (a la CheckForUpdates handler right now) of
	changes between the currently installed system and the
	downloaded contents in <directory>.  If <directory>'s values
	are incomplete or invalid for whatever reason, return
	None.  "Incomplete" means a necessary file for upgrading
	from the current system is not present; "Invalid" means that
	one part of it is invalid -- manifest is not valid, signature isn't
	valid, checksum for a file is invalid, or the stashed sequence
	number is not the running sequence number.

ApplyUpdate(directory, install_handler = None)
	This is essentially what Update does now, but i'll pick a different
	name because there are so many moving parts I will have to
	phase it out incrementally.  As with PendingUpdates(), it will
	have to verify the contents before it actually installs them, so
	the same questions about what to do with incomplete or
	invalid content applies.

Internally, there are also VerifyUpdate(directory), which
will verify the manifest, check that all the package files are there and
have the right checksum, and verify the stashed sequence, and
RemoveUpdate(directory), which will do the obvious.
Disabling SSLv2 and SSLv3
Disabling sslv2 & 3 (this time for apache)
Adding freenas boot pool status to the alerts (more stuff to come)
Adding the boot pool scrub button to the bootenv admin page

Fixing the fact that alerts should only exist when there are
no errors, or degradations, not alert when all is well
(sorry for not catching this earlier Jordan!)

Some other minor improvements.

More to come...
Typo fix.
Merge remote-tracking branch 'origin/master' into freebsd10