api: api no longer depends on state.

As part of a previous refactoring I accedently made api directly dependent on state, which is an even worse crime than state depending on the apiserver.

This proposal corrects this mistake and removes all dependencies on state from the api packages, along with additional removals of direct dependencies on state.

The cost is the agent package is responsible for translating between params.StateServingInfo, which is effectively the public data type of state information, and state.StateServingInfo which is the state's own version of the same.
state/toolstorage: remove old blob on update

If AddTools encounters existing metadata, it
will now attempt to remove the old blob. If
it fails to do so, an error will be logged
but not returned.
state: split toolsmetadata constant from others

Tools metadata does not represent entities in
the system like the other state collections.
Split it off like backups metadata.
Improve test coverage
Remove debugging printf
Merge pull request #710 from axw/state-toolstorage-addtools-remove-old

state/toolstorage: remove old blob on update

If AddTools encounters existing metadata, it will now attempt to remove the
old blob after adding the new one. If it fails to remove the old one, an error
will be logged but not returned.
Merge pull request #743 from davecheney/199-make-api-not-dependent-on-state

api: api no longer depends on state.

As part of a previous refactoring I accedently made api directly dependent on state, which is an even worse crime than state depending on the apiserver.

This proposal corrects this mistake and removes all dependencies on state from the api packages, along with additional removals of direct dependencies on state.

The cost is the agent package is responsible for translating between params.StateServingInfo, which is effectively the public data type of state information, and state.StateServingInfo which is the state's own version of the same.
Add reboot collection to state