Add Q&A (Installation) discussion form

[MohitGupta121]

Explanation

Add Q&A (Installation) discussion form

• This PR does the following: This is so we get all the information required to solve installation problems.

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

Proof that changes are correct

If your PR includes UI-related changes, then:

• Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
• For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
• Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
• Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

[MohitGupta121]

As @gp201 suggest me in last welfare meeting to do something similar for oppia-android.
@seanlip @gp201 @BenHenning PTAL, I make form similar as per oppia-web.

[BenHenning]

Thanks @MohitGupta121! This is interesting. Left a few comments after taking a first pass, PTAL.

[seanlip]

@MohitGupta121 I don't think you need a review from me on this. Please check with @gp201 on any dev-workflow-specific issues you run into, but otherwise, once @BenHenning approves this I think you can merge it.

Thanks!

[MohitGupta121]

@seanlip okay thanks, Waiting for @BenHenning and @gp201 review.

[gp201]

LGTM

[BenHenning]

Thanks @MohitGupta121. I think this looks really good! Excited to see how it works in practice.

[BenHenning]

Though it looks like you have a CI failure @MohitGupta121. Please fix & assign back.

[MohitGupta121]

Though it looks like you have a CI failure

Yes @BenHenning I see the checks are failing saying due to CODEOWNER files. So how I can passed that test?
Need to change anything in CODEOWNER file?

I think we need to need CODEOWNER for this file mentioned in the CI Check Failure

What do you suggest Ben is that correct, who is the CODEOWNER?

[MohitGupta121]

@BenHenning PTAL, all checks are passed now.

[BenHenning]

Thanks @MohitGupta121. This LGTM!