AddressSearch, Pins, ReverseGeocoder: Reference hell

[dopenguin]

Describe the bug
The selected result of a successful search may be updated without the intent of the user.

This happens in a typical configuration that can be e.g. found in snowbox.
There, a selected search result sets a pin, which triggers a reverse geocoding. The result of that gets added to the addressSearch input.

This leads to two problems:

• The user sometimes sees the loader for extended periods of time due to the unwanted reverse geocoding
• The changed result may confuse users

Expected behavior
The selected result may only be updated if the user selects a result or sets a pin themselves.

Steps to reproduce

1. Start snowbox
2. Search for "Billstraße"
3. Select "Billstraße"
4. The result gets updated to "Billstraße 144"

Additional context
This problem also occurrs on main as far as I can tell and thus should be fixed on both branches.

It is also possible that other plugins may have such cyclic references. It may be reasonable to tackle this issue in a generalized scoped.

[oeninghe-dataport]

Observations:

• This problem may occur with other plugin combinations, too. However, there are no combinations identified yet.
• The problem can only occur if the same store value is used as source and target by plugins.
• Programmatic changes of pin coordinates by other plugins or external code should (maybe) still trigger reverse geocoding.

Therefore, we need a mechanism that allows to detect the change source and behave accordingly. This mechanism should likely be implemented in usePluginStoreWatcher and be as generic and configurable as possible.

[dopenguin]

Fixed on next, open to be fixed on main