commenting out part of test that verifies DST cutover

Turns out my efforts to provide a proper unit test (using invariants) to check what happens during a DST cutover fails if the test is run in a zone like UTC (where DST is not observed).  This happens because the tagging monkey does not include timezone info in its tag, so in the unit test, while I specify Los Angeles, when the date is parsed out of the tag by a VM running in UTC, it will fail.

The test has some value, so I commented it out and left the appropriate explanation.  To re-activate it, there should be a mockable method that calculates Date values from tags in OldDetachedVolumeRule.