For #11498 and #11499 - Add Sync tabs error view (with/without CTA)

[BranescuMihai]

As per this documentation:

Sign-in error

No tabs error

Re-authenticate error

Pull Request checklist

• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
• Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

After merge

• Milestone: Make sure issues finished by this pull request are added to the milestone of the version currently in development.

To download an APK when reviewing a PR:

1. click on Show All Checks,
2. click Details next to "Taskcluster (pull_request)" after it appears and then finishes with a green checkmark,
3. click on the "Fenix - assemble" task, then click "Run Artifacts".
4. the APK links should be on the left side of the screen, named for each CPU architecture

[codecov-commenter]

Codecov Report

Merging #11634 into master will increase coverage by 0.06%.
The diff coverage is 23.02%.

@@             Coverage Diff              @@
##             master   #11634      +/-   ##
============================================
+ Coverage     27.51%   27.57%   +0.06%     
- Complexity     1006     1010       +4     
============================================
  Files           415      416       +1     
  Lines         16586    16655      +69     
  Branches       2127     2134       +7     
============================================
+ Hits           4563     4592      +29     
- Misses        11697    11732      +35     
- Partials        326      331       +5     

Impacted Files	Coverage Δ	Complexity Δ
...in/java/org/mozilla/fenix/AppRequestInterceptor.kt	84.00% <0.00%> (ø)	6.00 <0.00> (ø)
...a/org/mozilla/fenix/browser/BaseBrowserFragment.kt	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
...nix/components/toolbar/BrowserToolbarController.kt	69.88% <0.00%> (-0.98%)	0.00 <0.00> (ø)
.../mozilla/fenix/migration/MigrationStatusAdapter.kt	70.00% <0.00%> (ø)	5.00 <0.00> (ø)
.../mozilla/fenix/search/awesomebar/AwesomeBarView.kt	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
...java/org/mozilla/fenix/tabtray/FenixTabsAdapter.kt	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
...main/java/org/mozilla/fenix/tabtray/TabTrayView.kt	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
.../java/org/mozilla/fenix/tabtray/TabsTouchHelper.kt	10.63% <10.63%> (+10.63%)	0.00 <0.00> (ø)
...ava/org/mozilla/fenix/sync/SyncedTabsViewHolder.kt	54.28% <23.80%> (-45.72%)	1.00 <0.00> (ø)
...in/java/org/mozilla/fenix/sync/SyncedTabsLayout.kt	30.76% <33.33%> (+5.05%)	0.00 <0.00> (ø)
... and 8 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 239e3de...01a2465. Read the comment docs.

[codrut-topliceanu]

Looks good to me. Thanks.
I found some bugs unrelated to your PR that I will document in their own separate issues.

1. Cold starting Fenix and rushing to synced tabs fragment leads to some strange concurrency issues.
2. Being logged in on other devices with no tabs opened on them will lead to a blank page of synced devices instead of the "no tabs error".

Both issues are visible in this video : https://drive.google.com/file/d/14u83g7dp8Kjkw2G7LHjYdYJgbEGQ69Na/view?usp=sharing

[BranescuMihai]

Currently waiting on mozilla-mobile/android-components#7422 to get fixed on AC

[jonalmeida]

Cold starting Fenix and rushing to synced tabs fragment leads to some strange concurrency issues.

We have two bugs filed that needs more account manager support:

• Add SyncReason for engine requesting a sync android-components#7119
• Using a syncable storage in the correct state can lead to multiple syncs android-components#6879

[codrut-topliceanu]

@BranescuMihai Related AC issue/PR is now closed/merged

[BranescuMihai]

Progress: Still not merging this because there are some issues on AC that call refreshSyncedTabs twice, and the first time since the tabs are not yet synced, it will send to Fenix the NO_TABS error, leading to wrong UI behaviour. Will investigate after code freeze.

[ekager]

Product wants this CTA in our Sept release. Can we prioritize the blocking issues in AC or find a workaround @jonalmeida @BranescuMihai ?

[BranescuMihai]

Since the related bug is now explained in a different issue: #12195, and this PR is only about a UI change, we can proceed with this one