Allow ReadoutGeometry to be created from SQLite tables for GeoModelXml-based geometry tools
For Run4 geometry workflows, the primary input should be SQLite files. This means that the ReadoutGeometry must be able to be constructed from information contained there - specifically aux tables with the detector design parameters, and a list of FullPhysVols with key strings encoding which type of sensor they use, as well as information allowing the construction of Identifiers.
Prototype implementation for ITkStrip. This can be used as a template for ITkPixel and HGTD, or any other detector using GeoModelXml. Currently this gives different outputs than when building from Xml (the current workflow) but debugging will be easier once these changes are merged and can be tested in geometry-building pipelines. NB that this is not used in any production workflows currently.