Overrides of Writable fields are undone by first update notification from Consul

[lenny-goodell]

On startup we have always received an initial update notification from consul when nothing actually changed in consul. Previously when Consul was the Record of True this was not an issue.

Now it is an issue as overrides to Writable fields, which applied after loading from Consul, are undone when this initial update notification is processed. This only occurs when config already exists in Consul and a Writable filed that has an override has been changed in Consul or the override was added after to config was pushed into Consul

We somehow need to ignore this first bogus update notification from Consul.

[lenny-goodell]

Do the following to recreate this issue:

1. Stop edgex stack if running & Prune docker the volumes
2. Pull latest images
3. Start up the EdgeX stack (i.e. mongo-no-sect)
4. Verify data is flowing from device virtual by view logs for Core Data.
5. View logs for app-service-configurable-rules and see events are not being logged with level INFO
6. Edit compose file and add Writable_LogLevel: DEBUG to app-service-configurable-rules environment section
7. Restart app-service-configurable-rules
8. View logs for app-service-configurable-rules and see events are STILL not being logged since level is still INFO, but you do see override logged

'Writable.LogLevel' by environment variable: Writable_LogLevel=DEBUG"