Data Lake Data Connector updated

An issue causing the creation of duplicate variation IDs is now resolved. When multiple threads of the Data Lake Data Connector resend the same record to Data Lake, duplicate variation IDs can be created. Now, to prevent this timing issue, only one Data Connector thread is allowed to run per tenant. Additionally, the cached memory is now checked for duplicate records sent within 60 seconds of each other.