chore: adjust memory allocation for CI assemble and bundle tasks [WPB-8645]

[saleniuk]

https://wearezeta.atlassian.net/browse/WPB-8645

---

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?

Issues

“Release” variant builds fail on CI - the runner is canceled when executing :app:minify{Flavor}{Variant}WithR8.
Error only says that The operation was canceled.

Causes (Optional)

According to this article:
https://blog.jakelee.co.uk/gradle-build-freezing-on-github-ci/#cause--resolution
it can happen due to requesting too much RAM - in that case the runner can be canceled due to high usage and it can happen without any indication of OOM, just exactly like in our case.

Solutions

Limit the RAM usage in gradle.properties.

---

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud