Update NavigationView to guard against duplicate initializations

[danesfeder]

This PR aims addresses the original issue found in #1209 and removes the immediate need for #1239

In the NavigationView we were saying the View was "initialized" when navigation started. I think it makes more sense to check if NavigationMapboxMap is initialized and then have NavigationViewModel be the single source of truth for running navigation.

This should ensure 1 NavigationMapboxMap per 1 NavigationView. Creating more than one map per view was the issue I believe with the instrumentation tests.

[Guardiola31337]

Yeah, good point! Thanks for the quick fix here @danesfeder 🙏

Noting that this would resolve part of #1209 specifically the crash originated from our side CannotAddSourceException. We should keep digging into how to mitigate the other ones. Should we keep #1209 opened then? FWIW those happen rarely / less often.

[danesfeder]

@Guardiola31337 I updated, but did not close #1209 until we figure out the other issues. Looks like related to the Directions API request we do when starting up the test each time.

[Guardiola31337]

I updated, but did not close #1209 until we figure out the other issues.

Awesome, thanks!

Looks like related to the Directions API request we do when starting up the test each time.

Yeah, looks like it. Wondering if internet connection and/or using specific devices could be the cause of the issues 🤔