Fix: CodeCoverage report does not generated when ui tests are running under Test Orchestrator

[k4k7us23]

Changes description

• This PR fixes code coverage report generation, when ui tests are running under Test Orchestrator
• The issue is fixed both for connected devices and for gradle managed devices
• Due to the fix, configuration "connected-device-clear-package-data.yaml" was unignored
• A new test configuration for gradle managed devices under Test Orchestrator was added (gradle-managed-device-clear-package-data.yaml)

Fix explanation

• It turns out, that when tests are executed under Test Orchestrator, each test will produce it's own "*.ec" file with specific name. Please, see the screenshoot below, for better understanding
• 
• That is why, I have added generic build folder patterns to getExecutionDataFileTree() function

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.06%. Comparing base (dc9f71c) to head (544906c).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #118   +/-   ##
=========================================
  Coverage     86.06%   86.06%           
  Complexity       59       59           
=========================================
  Files             8        8           
  Lines           244      244           
  Branches         21       21           
=========================================
  Hits            210      210           
  Misses           13       13           
  Partials         21       21           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Rolf-Smit]

Sorry for being very late to review this. I have some small comments, but in general I think this looks good.

Thanks for jumping in and helping out with this project, really appreciated.

[Rolf-Smit]

@k4k7us23 again thanks for your help resolving this issue, greatly appreciated. I will soon create a release with this fix in it.

[Rolf-Smit]

@k4k7us23 just letting you know that this is now available in release 1.11.0, small heads up though, this release is based on the most recent stable Android Gradle Plugin release.