feat: disable QR code by feature flag (WPB-11921)

[yamilmedina]

WPB-11921 [Android] Implement a feature flag for QR code feature

---

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

It was defined that some changes needs to be discussed before release, so it's better to disable it for now, until new decisions are made.

Solutions

• Use a feature flag to disable the QR code screen
• Don't consider deeplink handling, since this is internal to the app, and will allow to open user profiles links (plain) that other clients might share (this was never ported from scala to reloaded)

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Open your user profile, there should not be a QR code button to open the screen.

---

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 SonarCloud

[github-actions]

Built wire-android-staging-compat-pr-3569.apk is available for download

[MohamadJaara]

can you also disable the processing of the deep link
@yamilmedina