chore: externalize all wire links to support custom builds (WPB-9811)

[yamilmedina]

WPB-9811 [Android] - C1, C2, C3 related Links are outdated- add new links as below - on Custom builds

---

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

For custom builds, we need to support external URLs not necessary into the wire website.

Causes (Optional)

Not supported / Out of initial scope

Solutions

• Move URLs to urls.xml file, so external builds can have their own if necessary.
• Fixes some URLs that were localized, this is not necessary since wire portal handles this according to the browser locale.

Note

Most of the changes are removing entries from strings resources, this can be ignored to have a better review.

---

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.

[github-actions]

Test Results

857 tests   857 ✅  9m 9s ⏱️
117 suites    0 💤
117 files      0 ❌

Results for commit 2be48b7.

♻️ This comment has been updated with latest results.

[MohamadJaara]

will the links be easier to customize if we add them to the default.json?

[yamilmedina]

Actually, I was talking yesterday with @vitorhugods, and we might not even need this file for public app.

We can just create an url.xml file in the specific builds resources directory, and the resource key will be overriden, so I think they are easy to customize with this approach or default json the same way. Just less Gradle config with this approach.

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

[github-actions]

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