Geographic Resources Data Migration Logic Update - Incorrect Logic (DDS-1071)

Logic for the data transformation for Geographic Resources need to include more logic around what should include the following values and not as currently Geographic Resources not from the BCGW have values populated that only relate to the BCGW.

This may be related to logic for 357 not populating Preview Info values.

**Logic** - this won't quite get them all but can build an exceptions list.

IF not already populated then:
1. Object Name like 'WHSE%' or Object Name like 'REG%' and
2. Resource Storage Location = 'BC Geographic Warehouse'

**Fields Populated**:
* **Resource Storage Format** = Oracle/SDE
* **Spatial Datatype**: = SDO_GEOMETRY
* **Projection Name** = ESPG_3005 - NAD83 BC Albers

examples of where these should not populated:
* This is in ArcGIS Online
...dataset/quesnel-natural-resource-district-2019-planting-blocks/resource/064b701e-a58f-48b0-a792-061fa7858d81
* This is from an Operational Database
... dataset/e1857418-3f63-43eb-911e-5a2f298c42f7/resource/8282e516-16cd-4485-a1f5-09ad385c0494
* These are a GeoPackage and FGDB on an FTP site
...dataset/30aeb5c1-4285-46c8-b60b-15b1a6f4258b

----
For BCGW WMS and KML Logic on how these are populated needs a bit more work.
* As these yes come from the BCGW and thus could have all that info but tecnically these are not in Albers.
* More thought on what fields are to be kept for WebServices as right now showing way more fields than what was in Cat Classic. Partially related to 312.