The production method is imported from Fenix:
    https://github.com/mozilla-mobile/fenix/blob/69020a1f269c57e86fb4eb1dfd25d3ea168b5a29/app/src/main/java/org/mozilla/fenix/ext/Activity.kt#L28

And was verified to address the issue it was added for.

Co-authored-by: Christian Sadilek <christian.sadilek@gmail.com>
Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>
Co-authored-by: Jonathan Almeida <jalmeida@mozilla.com>
Co-authored-by: Simon Chae <chaesmn@gmail.com>
Co-authored-by: Roger Yang <royang@mozilla.com>

to ContentBlocking.Setting.

We added the changes needed for Fenix to apply the policy settings they
need to the GeckoRuntime directly.

Since we require GeckoView changes to support the fix, we will let the
fix ride the train. However, to avoid breaking the build variants in
Fenix, we add the GeckoEngine extensions that are needed for the beta
variant. This would not give us the full benefits of the perf fixes,
but it will avoid regressing ETP changes should we upgrade the engine
and forget to apply changes we need for Fenix's GeckoProvider in beta.
Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>

This method can be used by clients to better estimate if fetchRegion() is
expected to take very little time as the region is already cached or if it can
take a bit longer since there are multiple operations / longer running
operations needed to actually fetch the region.

In the case of MozillaLocationService if the region is not already cached the
process of fetching the region involves a REST call with a connect / read
timeout of 10 seconds.

Issue #7647: Add SessionFeature.release() to allow app to stop rendering engine sessions and release the current one.

It missed the 48 train, so moving it to 49 instead.