Add Android release checklist for developers and QA

[colintheshots]

Adding a basic checklist of commonly-missed items to consider by developers and QA when releasing an Android app to the app store.

[mcomella]

Thanks for submitting! I think I need a little more context on how we expect to use this to figure out how we can best take advantage of this doc.

[mcomella]

In practice, how do you foresee this checklist being used? For example, is the release manager or QA expected to step through each item on the list before each release? Should developers go through the checklist when making a patch? Should this be used when setting up a new project to ensure we have a test case (manual or automated) for each item on the list?

Personally, I think a lot of these "checklist" items can be integrated into each app's Testrail test cases (they're manual test cases that QA runs for each release – example: Fenix – and they're like a super-checklist). This makes me think this could be a good resource for setting up new Android apps but I'm concerned that devs will not think to look for these docs when creating a new project. Is this what you were thinking? If so, do you know how to address this, "no one saw the documentation" problem?

We should probably check with QA how they set up the Testrail test cases for new apps too and see if there is any overlap here.