Migration of OsmBonusPack classes over to osmdroid

[spyhunter99]

MKergall/osmbonuspack#200 (comment)

after talking it over with @MKergall at OBP, sounds like we have concurrence to migrate the mentioned classes over to osmdroid. This will provide reduced complexity in osmdroid and reduce the somewhat cyclic dependency we have. OBP needs osmdroid, osmdroid deprecated PathOverlay saying to use OBP.

Anyhow this will be good for both projects

[spyhunter99]

merged

[MKergall]

You can remove all res/values directories => strings.xml only contains routing instructions, which are useless in osmdroid.

[MKergall]

In osmdroid/api, there are already a Marker and a Polyline class. They do nothing.
I don't know their purpose.
It can confuse to users, when using a Marker, to have to choose between "api" and "bonuspack" imports.
To be checked if they should be kept or not.

[spyhunter99]

the Marker class looks like an adapter for google maps via IMap which is "An interface that contains the common features of osmdroid and Google Maps v2. The marker class is used with the google wrapper only. Along with IMap and OnCameraChangeListener...

[spyhunter99]

i probably should have waited a bit to merge this. Although the code is there, it's not exactly integrated

[spyhunter99]

@MKergall i shuffled a bunch of stuff around with commit 181d855

all of the OBP overlay classes were moved into org.osmdroid.views.overlay
cache manager went to org.osmdroid.tileprovider.cachemanager

more an an FYI than anything else and to help get the migration plan started