Merge guidance view sub-type components into a single one

Refs https://github.com/mapbox/mapbox-navigation-android/pull/6239#pullrequestreview-1091711679.

This ticket tracks deprecating the `MapboxSignboardApi/View`, `MapboxJunctionApi/View`, and `MapboxSapaApi/View` (if introduced) classes, in favor of a `MapboxImageGuidanceApi` and `MapboxImageGuidanceView` (or something along these lines) that would expose distinct methods to download any of the sub-types and reuse the rest of the setup.

cc @abhishek1508 @kmadsen @tomaszrybakiewicz @cafesilencio

Start by reading the referenced pull request review and locating MapboxSignboardApi/View, MapboxJunctionApi/View, and MapboxSapaApi/View in the repository. Determine the intended unified MapboxImageGuidanceApi/View design and how each guidance sub-type should be exposed. Done means the deprecated sub-type components are replaced or deprecated in favor of the agreed single component without losing their setup behavior.

Written by the indexing model from the issue text.