abandoned: feat: added max-test-shards and client-details to additional-app-test-apks

[asadsalman]

Fixes #

This PR adds the ability to specify max-test-shards and client-details for tests under additional-app-test-apks like so:

additional-app-test-apks:
    - test: lib1-test.apk
      max-test-shards: 3
    - test: lib2-test.apk
      max-test-shards: 1
      client-details:
        modulename: lib2
        key2: val2

These configurations really improves support for multi-module projects, usually the thing I want to change the most is number of shards used to test a module. It also lets me differentiate between modules by setting key/values under client-details.

Test Plan

How do we know the code works?
Added unit tests.
.

Checklist

• Documented
• Unit tested
• Integration tests updated

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ @Sloox
❌ @asad Salman
Asad Salman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request}

[Sloox]

@asadsalman Hey can you sign the CLA bot to continue? If you are having issues with it or cannot sign it for legal reasons, please open an issue and we will implement this change for you.
There also will most likely be failing tests. Could you run a./gradlew clean build locally to ensure all is clear.

[asadsalman]

I have read the CLA Document and I hereby sign the CLA

[asadsalman]

I wrote up this draft to get early feedback on this approach. If it looks reasonable to you, I'm happy to proceed with fixing tests/linting/doc updates etc. I based my approach on this PR. Let me know if I should proceed.

[pawelpasterz]

cc @jan-gogo

[Sloox]

recheck

[Sloox]

Hey @asadsalman , please check slack in the firebase community, i have left you a direct message.

[asadsalman]

recheck

[jan-goral]

The implementation looks good, thanks! 👍

[Sloox]

Minor comment, else it looks fine by me 👍

[asadsalman]

This PR is now implemented by #1947 since a recent refactor introduced merge conflicts and it was easier to reimplement this as a new PR instead of rebasing and including all those new commits in this PR too.