IOVDbMetaDataTool fix

The IOVDbMetaDataTool was recently changed to move toward thread safety. The reset of the IOV range of an attribute collection was rewritten. This is needed, for example, for the simulation to be able to use a different run number when reading in IOV metadata from the input file. The changes had rewritten the logic - instead of creating a new one collection, the current one had its range reset. However, there was a slight mis-ordering of the sequence since the collection itself as well as each channel has an IOV range. Of course the collection IOV range should be at least as wide as the channels. The collection IOV range has to be reset last, because it is always 'shrunk' to be just large enough to encompass those of the channels. If one want to 'extend' the IOV range, then one has to do channels first, then collection. Otherwise, the collection IOV range will still have the 'old' IOV range if it is done first. Related to Jira: ATLASSIM-4501 Adding in @christos and @jchapman