Fix gce_campaignProximityTargetMap table - some criterionIDs are replicated across all targets within a campaign

As a result of one of the issues related to AML-867, SE campaigns with multiple proximity targets are being stored with the same criterionID for each. This results in API errors during radius boosts due to "duplicate elements".

Once AML-867 is deployed as part of 2.02 (or 1.5.1 for Optus), this data problem will no longer occur. Any existing SE campaigns with multiple proximity targets will have to be fixed by assigning the proper criterion to each target.

From comments in AML-867: "....you will have to fix the gce_campaignProximityTargetMap table. The criterionID values in this table are wrong when there is more than one target per SE campaign."

A script is needed to retrieve the proper criterion ID for each proximity target and to update the db with the proper value.