Adding smoke and regression tags to tests

[cortisiko]

Development & PR Process

1. Follow MetaMask Mobile Coding Standards
2. Add release-xx label to identify the PR slated for a upcoming release (will be used in release discussion)
3. Add needs-dev-review label when work is completed
4. Add needs-qa label when dev review is completed
5. Add QA Passed label when QA has signed off

Description

The time it takes to build and launch tests on bitrise is >90 mins. To prevent tests from timing out on bitrise, we need to add specific tags @smoke @regression on the different E2E tests. We need a better way to specify tags. We should create a constants file for all of our tags. then have a command line flag to run specific tags. For example, if we want to run all tests with the smoke tag we wun do something like this:

yarn test:android:qa --tags=smoke

Screenshots/Recordings

If applicable, add screenshots and/or recordings to visualize the before and after of your change

Issue

Progresses #???

Checklist

• There is a related GitHub issue
• Tests are included if applicable
• Any added code is fully documented

[smoke]

@cortisiko Hey, sorry to bother on this PR, but can I kindly ask you to mark tags as code using
` e.g. @smoke @regression instead of just @smoke @regression.
It is not a big deal, but otherwise GitHub uses those as handles and you risk "summoning" someone unintentionally.

I love Metamask it is great product, keep up the good work!

[cortisiko]

oh my apologies @smoke, I was unaware that there was a gh profile associated with " @ smoke". I will format the text in the ticket description now.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Fatxx]

As an increment to this PR I added the following:

• Splited build_android_qa and wdio_android_e2e_test in to separate workflows, at the end of build_android_qa wdio_android_e2e_test is triggered in a separate build this will help us avoid build timeouts in Bitrise;
• Added support for the following environment variables: BROWSERSTACK_DEVICE, BROWSERSTACK_OS_VERSION, BROWSERSTACK_TAG_EXPRESSION and BROWSERSTACK_APP_URL in wdio/config/android.config.browserstack.js they can now be declare when triggering a build in Bitrise which enable more customisation
• Updated docs: https://www.notion.so/E2E-Testing-361fee8ff65048f0b18d6d3dddc5ad9c