Fixed issue with balances not syncing on balance adjustments
Fixed issue where data wasn't being imported into interim loyalty database, due to invalid characters within the .CSV extracts
Added the ability to run a historic import to SQL database (so it doesn't send it to REST). This will help with future troubleshooting and make it easier to catchup any missing data
Added a delay into how fast the integration pushes the configs through, the recent updates to the REST node caused us to process the configs too quickly - resulting in unexpected behaviour
Historic imports used to generate PoPs on the import date, we now only generate PoPs on a visit
We used to generate PoPs based on a balance adjustment, but a balance adjustment might be for non-visit related purposes (i.e. Expired points). We now generate PoPs based on a Visit flag provided in a new file we consume - loyalty_transactions
