Issue Description: 

Our first implementation of the synchronization logic between control plane and data plane for v2 simply sends all statuses on a timed loop to prevent lost updates.

A concern is that many of these updates are not necessary as for the majority of resources, nothing will have changed and this results in unnecessary update queries on the Control Plane.

The purpose of this task is to provide a mechanism for the data plane to avoid sending period updates for resources that have not changed since the last update to the control plane.

Acceptance Criteria: 

• The Data plane will exclude any resources from its periodic update to the Control Plane that have not changed

Additional Information: 

• This implementation must be in-memory and not use any other persistent storage to maintain our simple deployment model
• Consider Quarkus caching options for managing the previous version of a resource sent to the control plane.