chore: ci unit test tunning

[yamilmedina]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Slow or unnecessary steps in pipeline, test also run slow, and we can take advantage of parallelism of jupiter

Solutions

Tune configurations for tests and remove not used step in Jenkins

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[yamilmedina]

Never used by jenkins or as an output of jenkins, coverage runs on GH actions.

[github-actions]

Test Results

678 tests  ±0   678 ✔️ ±0   9m 52s ⏱️ - 2m 44s
  98 suites ±0       0 💤 ±0 
  98 files   ±0       0 ❌ ±0 

Results for commit edc1d01. ± Comparison against base commit f666c81.

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!