Add AlternateTag to GEP Synchronizations

[ritchiecarroll]

DataPublisher does not include AlternateTag in its MeasurementDetail dataset for synchronization. Additionally, DataSubsriber currently uses the field to account for proper assignment of SignalID where new records in some databases trigger the creation of a new UUID but the synchronization process needs to make sure the remote and local SignalID values match - afterwards the DataSubscriber sets the hijacked AlternateTag field to NULL.

Ideally the AlternateTag could also be synchronized since this is becoming a more important field especially in deployments that use OSI-PI or other historians where a custom tag name is desirable.