[Poll] Error handling for push rules synchronization

[Florian14]

Type of change

• Feature
• Bugfix
• Technical
• Other :

Content

Display an error in the settings screen when push rules are out of sync (after opening the screen or modifying the rules)

Added a live refresh of the notification setting screens when the account data is updated (eg. from another client)

Motivation and context

Error handling of the new push rules introduced in #8114

Screenshots / GIFs

Tests

On a synapse supporting the new push rules

• update the default rules in the notification settings (Direct messages and/or group messages fields)
• break the sync of the rules by editing the push rules entry in the account data (using /devtools from a web instance)
• verify that an error is displayed upon the broken rule

Note that the rules should be automatically realigned by #8130 so the error may be not visible

Tested devices

• Physical
• Emulator
• OS version(s):

Checklist

• Changes has been tested on an Android device or Android emulator with API 21
• UI change has been tested on both light and dark themes
• Accessibility has been taken into account. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#accessibility
• Pull request is based on the develop branch
• Pull request includes a new file under ./changelog.d. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#changelog
• Pull request includes screenshots or videos if containing UI changes
• Pull request includes a sign off
• You've made a self review of your PR
• If you have modified the screen flow, or added new screens to the application, you have updated the test UiAllScreensSanityTest.allScreensTest()

[ElementBot]

• ⚠️ It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.
• ⚠️ It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

72.2% Coverage
0.0% Duplication

[yostyle]

LGTM