[BUG] bounds potentially broken in MapOptions

[JaffaKetchup]

Describe The Bug
The bounds may argument have no effect when loading the map when specified inside MapOptions, depending on how the FlutterMap widget is laid out.

Expected Behavior
The map should initially load with the view inside the specified LatLngBounds, in all cases.

Additional Information
Using a MapController to move the map into bounds seems to always work - use as a workaround for now.
This issue was initially discussed in #1211 since #1211 (comment).

---

To Reproduce
Steps to reproduce the behaviour:

I just tested it with the examples home page. One thing as mentioned I dug out, was that certain outer widgets can cause issues, like Columns which the examples use (hard to know if thats relevant here). I tried to add an Expanded widget which one SO answer to a similar problem suggested, but that was outside the Layout builder which may not help. - Written by @ibrierley in #1211 (comment)

---

Severity
This will help us to label the issue quicker and decide what needs attention first. Only choose fatal if the entire app crashes, otherwise choose non-fatal.

• Non-Fatal
• Fatal / App Crashes

Frequency/Rarity
This will help us to label the issue quicker and decide what needs attention first.

• Once
• Uncommon
• Common
• Always

Applicable Platforms
Only select those that you've tested on - one or more. If possible, test on a variety of platforms.

• Unknown/All
• Android
• iOS
• Web
• Windows
• Others (beta platforms)