fix: Conversation proteus verification

[borichellow]

What's new in this PR?

Issues

1. verification statuses of "my" clients were ignored in calculating conversation verification status
2. Conversation verification status was not affected after adding/removing members into the conversation
3. when the new group conversation is created it automatically gets a system message that the conversation verification was degraded.

Causes (Optional)

1. not implemented
2. not implemented
3. didn't know it's an issue

Solutions

1. implement it by checking "my clients" in calculating the conversations verification status (ignore 1 clients status, as it's my current client)
2. add trigger for members changes, to re-calculate conversation status
3. update addMessageAfterProteusVerificationStatusChange trigger to work only if new or prev status is VERIFIED, so trigger doesn't run when status changes : not_verified -> degraded.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Unit Test Results

   382 files   -   82     382 suites   - 82   26s ⏱️ - 4m 5s
2 227 tests  - 362  2 161 ✔️  - 324  66 💤  - 38  0 ❌ ±0 

Results for commit fcd8396. ± Comparison against base commit bfcae0a.

♻️ This comment has been updated with latest results.

[datadog-wireapp]

Datadog Report

All test runs 13e8b9e 🔗

✅ 2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed

Test Services

Service Name	Failed	Known Flaky	New Flaky	Passed	Skipped	Wall Time	Branch View
kalium-ios	0	0	0	2161	66	5m 44.08s	Link
kalium-jvm	0	0	0	2485	104	11m 41s	Link