Fix part of #3600: Add tablet UI for FAQs and Third-party Dependencies

[prayutsu]

Explanation

Fixes part of #3600:
Added new UI for tablet devices for HelpActivity that shows FAQs List and Dependencies List

Mock Link - https://xd.adobe.com/view/d405de00-a871-4f0f-73a0-f8acef30349b-a234/screen/dae1f41b-9551-430e-8b61-b285d6ee050b/

Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
• The PR follows the style guide.
• The PR does not contain any unnecessary auto-generated code from Android Studio.
• The PR is made from a branch that's not called "develop".
• The PR is made from a branch that is up-to-date with "develop".
• The PR's branch is based on "develop" and not on any other branch.
• The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

Screenshots -

Portrait	Landscape

3 test cases failing on espresso that are only meant for phones.

[oppiabot]

Unassigning @rt4914 since the review is done.

[oppiabot]

Hi @prayutsu, it looks like some changes were requested on this pull request by @rt4914. PTAL. Thanks!

[rt4914]

@Test
  fun testHelpFragment_parentIsNotExploration_checkBackArrowNotVisible() {
    launch<HelpActivity>(
      createHelpActivityIntent(
        internalProfileId = 0,
        isFromNavigationDrawer = true
      )
    ).use {
      onView(withContentDescription(R.string.abc_action_bar_up_description))
        .check(doesNotExist())
    }
  }

This test case has started failing on espresso if run on a tablet device because we now have two buttons in tablets with the same contentDescription.

We may want to change the description for one of the back buttons.
Note that we could modify the test to match the visibility to GONE but that might not be a good idea because the test case aims to verify that the back button is not present in the main toolbar when HelpActivity is loaded from Exploration.

Also, I just noticed that the back button isn't shown in mocks as there is no use of the back button on this screen until the license list or license texts are displayed.
So, I just hid the back button for these screens and modify the test cases accordingly.

Makes sense. We will need to change content description and I think we can use Navigate back to $s where s can be Third Party Dependency list or Copyright Licences depending upon which fragment is currently shown.

[prayutsu]

@rt4914 The test case is now fixed -

[rt4914]

LGTM, thanks.

[BenHenning]

Thanks @prayutsu. Had a few comments--PTAL.

[BenHenning]

Thanks @prayutsu. LGTM for codeowners.

[BenHenning]

Given everyone has approved & there are no unresolved conversation threads, merging this.