Store transaction profiles in capped db

They can be very large, better to cap them. Seems ok to store them in
same capped db as trace details so transaction details will expire at
same time as trace details.
Expire transaction point data
Update global nav menu text and order
Update dependencies
Disable H2 shutdown hook even in tests with memdb
Fix the ordering of lists in config.json

So the config.json file doesn't get re-ordered each time it is written
out.
Use fixed delay instead of fixed rate

This seems safer in case full GC or other system slows down system and
backlogs the scheduled commands.
Continue re-capturing stuck threads at interval
GC Events, navbar changes and related refactoring
MBeans
TEMP SAUCE LABS ON TRASK/GLOWROOT
Gauges