FIX: Guard ring contact handling when loading 4-column strip map files

[fhagemann]

Fixes #216:
For strip map files with only 4 columns, we infer information about RTB, DRM, IsPrimary, ASICID and Channel from the ReadOutID. The way we were doing that so far was wrong for guard ring contacts, and also the RTB and DRM values were wrong for all strip contacts.

This PR contains two fixes:

• correctly handle GR contacts when loading a 4-column strip map file
• assign the correct RTB and DRM when loading a 4-column strip map file

Note: this is somewhat hard-coded for what we expect for COSI and might be different for GRIPS.

[fhagemann]

To test this, we could create a 4-column strip map file from a 9-column strip map files (just keeping the first and the last three columns), and check that if we generate a strip map from the "full" 9-column strip map file and the "compact" 4-column strip map file, the stored MStripMap is identical (?)

[zoglauer]

Well, I saw what you wrote before, guess we see if it works when we have the real data?

[fhagemann]

I tested this on a file containing only pulser data, but with 4 active detectors.
Pre-PR I was getting this error using a 4-column strip map file:

MStripMap: ASIC polarity update creates a duplicate detector/side/strip tuple for detector 0 strip 64
XmlTagMeasurementLoaderHDF: Unable to update ASIC polarities based on the config JSON.

Now with the changes in this PR, I don't get the error anymore and the results look reasonable.