Check relevant registration properties for whiteboard services

The trackers for any whiteboard service always deactivate and activate the corresponding service on a modified event. If now any property on a whiteboard service changes, this causes the reactivation - which (especially for servlet context helpers) can result in a lot of churn.
We should rather see if relevant properties have been modified and only then do the reactivation