Benchmark and optimize class lookups

When https://github.com/mapbox/mapbox-base-android/issues/14 is closed, we can look into running benchmarks on release builds and measuring the impact of reflection class lookups. https://developer.android.com/jetpack/androidx/releases/benchmark looks like a good tool that we can use.

Optimization ideas, TBD:

• potentially, kotlinf-reflect is able to cut down invoke calls and class lookup times. We'd need to evaluate binary size increase vs performance improvements if those are confirmed
• for all other clients that are not building from source but consuming the pre-built binary instead, we could hardcode the glue classes paths and avoid the reflection overhead

Inizia controllando l’issue prerequisito #14 e la documentazione di AndroidX Benchmark. Esegui il benchmark delle build di release per misurare le prestazioni della ricerca delle classi tramite reflection, quindi valuta i compromessi in termini di dimensioni binarie e prestazioni tra kotlin-reflect e i percorsi hardcoded glue-class. L’attività è completata quando le alternative hanno risultati misurati e una direzione di ottimizzazione documentata.