Fix parent path introspection data invalidation for multiple levels
Fix parent path introspection data invalidation for multiple levels

In the case that parent path data needs to be invalidated we shouldn't
stop at the immediate parent if it doesn't have our own handler
registered but should continue upwards in the tree until we reach root
or our own handler.

pkarasev3/bluez,silent-snowman/bluez,silent-snowman/bluez,silent-snowman/bluez,mapfau/bluez,ComputeCycles/bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,mapfau/bluez,ComputeCycles/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,ComputeCycles/bluez,silent-snowman/bluez,pkarasev3/bluez,pkarasev3/bluez,ComputeCycles/bluez,pkarasev3/bluez