Update version to 48.0.1.

Issue mozilla-mobile#7553: (Merge day) browser-engine-gecko-nightly (…

…79) -> browser-engine-gecko-beta (79)

Merge mozilla-mobile#7456 mozilla-mobile#7457 mozilla-mobile#7458

7456:  Docs update (20200622-120839) [ci skip] r=pocmo a=MickeyMoz



7457:  GeckoView update (beta) (20200622-140320) r=pocmo a=MickeyMoz



7458:  GeckoView update (nightly) (20200622-140318) r=pocmo a=MickeyMoz



Co-authored-by: MickeyMoz <[email protected]>

Set version to 46.0.0

Set version to 44.0.1.

Merge mozilla-mobile#7200

7200: Closes mozilla-mobile#6815: Remove deprecated isUrlLikeStrict method r=mcomella a=csadilek

r? @mcomella time to say goodbye to this :)

Co-authored-by: Christian Sadilek <[email protected]>

Merge mozilla-mobile#7100

7100: Issue mozilla-mobile#7011: Correctly evaluate memory trimming levels. r=psymoon a=pocmo

Previously we assumed the value passed to onTrimMemory() represents a single linear progression of memory limits. But this
is not the case. We need to look at the values individually.

See:
https://developer.android.com/reference/android/content/ComponentCallbacks2


Co-authored-by: Sebastian Kaspari <[email protected]>

Update GeckoView Beta to 77.0.20200526221856.

Update GeckoView Beta (77.0.20200518175620) version.

Merge mozilla-mobile#6964

6964: Initialize accountManager on the main thread during migration r=pocmo a=grigoryk

Fenix bug for this - mozilla-mobile/fenix#10432

This fixes fallout from mozilla-mobile#6395 in which
FennecMigrator changed to accept a Lazy-wrapped reference to the account manager.

This was done so that during regular (non-migrating) startup, a simple act of building a no-op
migrator will not cause account manager initialization.

However, during a migrating startup this creates a race to initialize account manager.
Two participants in this race are:
1) FenixApplication running expensive operations (such as storage init, account manager init)
after visual completeness. However, currently that just entails a 5 second delay from `onStart`.
2) FxA migration, which runs roughly at the mid-point of the migration.

Account manager currently can't be initialized on a background thread (or it will crash).
FxA migration runs on a background thread, so if (2) wins (that is, migrations before FxA migration take
less than 5 seconds), then migration will crash.

This patch adds an eager initialization right before we kick-off migrations but are still on the main thread,
iff an FxA migration will be executed.



Co-authored-by: Grisha Kruglov <[email protected]>