[FIX] Appium: Notify appium server test is done

[chrisleewilcox]

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
Some tests will fail after test run even if all steps pass which causes issues with results and reports. This was due to our wdio automation not notifying appium that the test has completed, which would cause some callbacks to fail after the test because the callbacks refer to a test sessionID that no longer exist because the sessionID was terminated after the test. You can see the bug by looking at the bitrise logs that is linked to the issue reported.

This change will notify appium that a sessionID has completed and any outstanding callbacks that reference sessionID's that no longer exist will be handled by appium and no failure/error is generated after the test.

Fixes: reporting a failed test after test run even though all test steps passed, reporting the test correctly.
Fixes: callbacks that refer to a terminated/expired test sessionID to be handle without reporting a failure.

Screenshots/Recordings
Bitrise report for all test.
Smoke test on browserstack with CreateNewWallet.feature that was consistently getting the error. All smoke tests pass .

Issue

Progresses #949
Progresses #5845

Checklist

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

[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.

[sethkfman]

LGTM