Properly reset DQMStore after bookTransaction call

When enableMultiThreading was turned on, the Harvesting step was
crashing. The problem was traced down to one DQMEDAnalyzer in the
job which was setting the value for run_, streamId_ and moduleId_
and then those values were being applied to legacy modules who called
DQMStore. By resetting the values of those variables back to what
they were before the call to bookTransaction the jobs now run correctly.
Merge pull request #3466 from Dr15Jones/properlyResetDQMStoreAfterTransaction

DQM -- Properly reset DQMStore after bookTransaction call