6077: Closes #6058: Replace IntentService with JobIntentService for crash handler r=jonalmeida a=rocketsroger



Co-authored-by: Roger Yang <royang@mozilla.com>

6072: Bug 1615248 - add beetmover jobs in the nightly graphs r=JohanLorenzo,pocmo a=MihaiTabara

Now that we have fully functional builds + signing in the AC nightly graphs, time to add beetmover counterpart as well. Artifacts generated are going to go under https://nightly.maven.mozilla.org/

, for example:

```
maven2/org/mozilla/components/browser-awesomebar/34.0.20191005130104/browser-awesomebar-34.0.20191005130104-sources.jar.asc
maven2/org/mozilla/components/browser-awesomebar/34.0.20191005130104/browser-awesomebar-34.0.20191005130104-sources.jar
```

I checked with `taskgraph-diff`, there are no other changes in the `release` or `snapshots` graph. The PR only adds the beetmover counterparts. 

I won't land this until I'm done with the changes in the beetmoverscript, cloudops-infra and SOPS too for all the credentials stuff. 

Co-authored-by: Mihai Tabara <mtabara@mozilla.com>

5916: For #5557 Get Cert Issuer Name r=csadilek a=kglazko



Co-authored-by: Kate Glazko <katglazko@gmail.com>

6078: Submit caught exceptions while updating add-ons to the crashReporter r=psymoon a=Amejia481



Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>

6071: Closes #6070: Mark badgeView invisible if it's null r=Amejia481 a=psymoon



Co-authored-by: Simon Chae <chaesmn@gmail.com>

6060: Update to application-services 0.52.0. Fixes #5999 r=grigoryk a=mhammond



Co-authored-by: Mark Hammond <mhammond@skippinet.com.au>
Co-authored-by: Grisha Kruglov <gkruglov@mozilla.com>

6067: Bump nokogiri from 1.10.4 to 1.10.8 in /docs r=jonalmeida a=dependabot[bot]

Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.4 to 1.10.8.
<details>
<summary>Release notes</summary>

*Sourced from [nokogiri's releases](https://github.com/sparklemotion/nokogiri/releases).*

> ## 1.10.8 / 2020-02-10
> 
> ### Security
> 
> [MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in [#1992](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1992). Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.
> 
> 
> 
> ## 1.10.7 / 2019-12-03
> 
> ### Bug
> 
> * [MRI] Ensure the patch applied in v1.10.6 works with GNU `patch`. [#1954](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1954)
> 
> 
> 
> ## 1.10.6 / 2019-12-03
> 
> ### Bug
> 
> * [MRI] Fix FreeBSD installation of vendored libxml2. [#1941, [#1953](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953)] (Thanks, [@&#8203;nurse](https://github.com/nurse)!)
> 
> 
> 
> ## 1.10.5 / 2019-10-31
> 
> ### Dependencies
> 
> * [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
> * [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34
> 
> 
</details>
<details>
<summary>Changelog</summary>

*Sourced from [nokogiri's changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md).*

> ## 1.10.8 / 2020-02-10
> 
> ### Security
> 
> [MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in [#1992](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1992). Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.
> 
> 
> ## 1.10.7 / 2019-12-03
> 
> ### Fixed
> 
> * [MRI] Ensure the patch applied in v1.10.6 works with GNU `patch`. [[#1954](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1954)]
> 
> 
> ## 1.10.6 / 2019-12-03
> 
> ### Fixed
> 
> * [MRI] Fix FreeBSD installation of vendored libxml2. [[#1941](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1941), [#1953](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953)] (Thanks, [@&#8203;nurse](https://github.com/nurse)!)
> 
> 
> ## 1.10.5 / 2019-10-31
> 
> ### Security
> 
> [MRI] Vendored libxslt upgraded to v1.1.34 which addresses three CVEs for libxslt:
> 
> * CVE-2019-13117
> * CVE-2019-13118
> * CVE-2019-18197
> * CVE-2019-19956
> 
> More details are available at [#1943](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1943).
> 
> 
> ### Dependencies
> 
> * [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
> * [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34
</details>
<details>
<summary>Commits</summary>

- [`6ce10d1`](https://github.com/sparklemotion/nokogiri/commit/6ce10d15d7af6ad65813a495eaf168f73eba211c) version bump to v1.10.8
- [`2320f5b`](https://github.com/sparklemotion/nokogiri/commit/2320f5bd6319dca9c68d85bbf41629bbf8052a49) update CHANGELOG for v1.10.8
- [`4a77fdb`](https://github.com/sparklemotion/nokogiri/commit/4a77fdb789aefed7ca65c7c7f57ad4dca0d3b209) remove patches from the hoe Manifest
- [`570b6cb`](https://github.com/sparklemotion/nokogiri/commit/570b6cbc5fbc5ee7ef969332c587b951ae35bcd0) update to use rake-compiler ~1.1.0
- [`2cdb68e`](https://github.com/sparklemotion/nokogiri/commit/2cdb68e95aa075ac36a08d4d82d9b410a950a051) backport libxml2 patch for CVE-2020-7595
- [`e6b3229`](https://github.com/sparklemotion/nokogiri/commit/e6b3229ec53ddf70f1d198bba0d3fc13fde842a8) version bump to v1.10.7
- [`4f9d443`](https://github.com/sparklemotion/nokogiri/commit/4f9d443c2fddc40eefec3366000861433aff6179) update CHANGELOG
- [`80e67ef`](https://github.com/sparklemotion/nokogiri/commit/80e67ef636ce0ddd55a4a7578d7bbdb186002560) Fix the patch from [#1953](https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953) to work with both `git` and `patch`
- [`7cf1b85`](https://github.com/sparklemotion/nokogiri/commit/7cf1b85a5f8033252e55844ab2765e8f612d4d89) Fix typo in generated metadata
- [`d76180d`](https://github.com/sparklemotion/nokogiri/commit/d76180d0d26a7afb76d84e0de2550ac3bb6abb15) add gem metadata
- Additional commits viewable in [compare view](https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8)
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=nokogiri&package-manager=bundler&previous-version=1.10.4&new-version=1.10.8)](https://help.github.com/articles/configuring-automated-security-fixes

)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)



Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

6076: Closes #6075: Create a migration for SitePermissionsDatabase to introduce autoplay fields. r=csadilek a=Amejia481



Co-authored-by: Arturo Mejia <arturomejiamarmol@gmail.com>

autoplay fields

6074: Closes #6073: Adds animation to showPopupWhereBestFits menu r=Amejia481 a=sblatz



Co-authored-by: Sawyer Blatz <sdblatz@gmail.com>

6063: Support appServerKey and complete callbacks for push subscription failures r=rocketsroger a=jonalmeida



Co-authored-by: Jonathan Almeida <jalmeida@mozilla.com>

6069:  GeckoView update (nightly) (20200225-141408) r=psymoon a=MickeyMoz



Co-authored-by: MickeyMoz <sebastian@mozilla.com>

6066:  Docs update (20200225-120900) [ci skip] r=pocmo a=MickeyMoz



Co-authored-by: MickeyMoz <sebastian@mozilla.com>

6064: Bug 1615248 - fix paths in build jobs; add signing jobs in nightly releases r=JohanLorenzo,pocmo a=MihaiTabara

Follow-up from https://github.com/mozilla-mobile/android-components/pull/5967/ - to fix the build paths. The artifacts are correctly generated by gradle (as they would for a normal github release), and renamed correctly to encompass the `buildid` within them. But I initially thought I need to amend the version as well (like GV does) but that is not needed as we can do that directly in beetmover. 

After all, the renaming script, at runtime, renames only individual filenames, not folders. So I should've done the same at generation time, and not touch the folders.

This is pretty much revert to what we used to have before I landed my PR, in this particular piece of code.

Local diff:
```
331c331
<             "path": "/builds/worker/checkouts/src/components/browser/awesomebar/build/maven/org/mozilla/components/browser-awesomebar/34.0.20200212190116/browser-awesomebar-34.0.20200212190116-sources.jar",


6065: Fix for #5996 - Update complete notification is not routing to onboarding screen r=pocmo a=Sparky93

### Pull Request checklist
<!-- Before submitting the PR, please address each item -->
- [x] **Quality**: This PR builds and passes detekt/ktlint checks (A pre-push hook is recommended)
- [x] **Tests**: This code is already covered by tests
- [x] **Changelog**: This PR does not need a changelog entry
- [x] **Accessibility**: The code in this PR does not include any user facing features

### After merge
- [ ] **Milestone**: Make sure issues closed by this pull request are added to the [milestone](https://github.com/mozilla-mobile/android-components/milestones) of the version currently in development.
- [ ] **Breaking Changes**: If this is a breaking change, please push a draft PR on [Reference Browser](https://github.com/mozilla-mobile/reference-browser) to address the breaking issues.

### PLEASE MERGE THIS BEFORE IT'S FOLLOW UP [ISSUE](https://github.com/mozilla-mobile/fenix/issues/8722

) ON FENIX


Co-authored-by: Mihai Tabara <mtabara@mozilla.com>
Co-authored-by: Sparky93 <andrei.a.lazar528@gmail.com>

Made out class constraint more permissive in migration service.

Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.4 to 1.10.8.
- [Release notes](https://github.com/sparklemotion/nokogiri/releases)
- [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md)
- [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8

)

Signed-off-by: dependabot[bot] <support@github.com>

6054: Closes #6053: Register an account state persistence callback for offline migration recovery r=pocmo a=grigoryk

This fixes a problem where an account state persistence callback was not registered
during the recovery part of the offline fxa migration flow.

This caused us to successfully migrate, but then migrate again and again (always successfully)
upon application restart, since we wouldn't remember our own success.




Co-authored-by: Grisha Kruglov <gkruglov@mozilla.com>