Future of plugins repository

Nobody has claimed this yet.

I had been discussing with @louwers also re. https://github.com/maplibre/maplibre-native/issues/1151#issuecomment-1551501601 how to structure the Android-specific code.

I notice that there is currently some deprecated annotations code in maplibre native, and a non-deprecated (but highly confusingly essentially duplicate) implementation here in the plugins. Most of the maplibre plugins are currently also unmaintained.

It can also be confusing for developers that there's two separate sample apps (one for maplibre-plugins-android and one for maplibre-native android).

For these reasons we think that the current situation is rather messy and should be cleaned up. One possibility would be to move the plugins into maplibre-native.

Possible benefits (if done correctly):

* remove deprecated code and replace it with working one
* less confusing structure
* tighter integration has benefits regarding APIs for users (more sensical structure)

Start by reading this issue and the linked MapLibre Native discussion about structuring Android-specific code. Compare the deprecated annotations implementation, its duplicate in the plugins, and the two sample apps to identify the affected scope. Done requires an agreed structure and migration plan before implementation can be divided into concrete changes.

Written by the indexing model from the issue text.