Unnecessary map initialization performance penalty caused by delaying composing GoogleMap() subcomposition until after GoogleMap object is available

android-maps-compose 4.3.0

From code inspection I've noticed that there is an undue performance penalty caused by delaying the `GoogleMap()` subcomposition until after the `GoogleMap` object has been made available via suspending `MapView.awaitMap()`.

While the `GoogleMap` object is required during the "apply changes" phase of the subcomposition, it should not be required to perform the initial composition of the subcomposition, prior to "apply changes".

Initial composition phase of subcomposition and `MapView.awaitMap()` should and can be performed in parallel.