fix: refactor cvmfs freshness test

Previous version was just comparing revision numbers, and this resulted in many false-positives (multiple revisions may be deployed to Stratum-0). To avoid this, let's use a different approach: only check revision difference if the cvmfs manifest is "old enough" (created 1 hour ago or later).

Thanks to @cburr for this idea.