requeue recently fetched components

We have cases now where the definitions are being built from reasonably old harvested data and as a result the definitions are substantially out of date. Previously we talked about having the service check the current crawler tool levels and requeue any definition based on older tools. We'd still return the old definition but soon enough the new one would be ready.

Thoughts:
* pretty soon now we are going to rescan the world so we'll be up to date
* pretty soon after that we'll do some sort of change that will make those obsolete
* There is an issue if we do this lazily where the same thing could get queued many times causing queue bloat and even duplicate work for long running tools.
* may be better to do it as a "job" where we periodically queue up "old" definitions.

Summary:
* we can defer for a bit but should put this in place relatively soon after rescanning everything

thoughts @dabutvin ?