[Poll] Synchronize polls push rules with message push rules (PSG-954)

[Florian14]

Type of change

• Feature
• Bugfix
• Technical
• Other :

Content

Add the new push rules for the polls related to the MSC3930.
Bind the new rules in the notification settings with the existing rules for direct messages and group messages.

Also:

• deleted unused advanced notifications fragment
• renamed notification settings classes (removed Preference from the class names)

Motivation and context

Close #8007

Note: the error handling and the initial sync of the rules when they are received from the server will be done in dedicated PRs.

Screenshots / GIFs

Tests

Needs a server supporting the new MSC for testing

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]

	Warnings
⚠️	vector/src/main/java/im/vector/app/features/settings/notifications/VectorSettingsPushRuleNotificationFragment.kt#L83 - It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.
⚠️	vector/src/main/java/im/vector/app/features/settings/notifications/VectorSettingsPushRuleNotificationFragment.kt#L83 - It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.
⚠️	vector/src/main/java/im/vector/app/features/settings/notifications/advanced/VectorSettingsAdvancedNotificationPreferenceFragment.kt#L95 - It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.
⚠️	vector/src/main/java/im/vector/app/features/settings/notifications/advanced/VectorSettingsAdvancedNotificationPreferenceFragment.kt#L95 - It will always be more efficient to use more specific change events if you can. Rely on notifyDataSetChanged as a last resort.

Generated by 🚫 dangerJS against 0a0ad2d

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

32.9% Coverage
0.0% Duplication

[jonnyandrew]

Is it worth doing this now while we're already making changes to notification preference screens?

[Florian14]

I removed it initially but it involved also removing the related resources. I preferred to revert to not include more changes in the PR and I was wondering if it could be used in f-droid (even if I did not find any usage). Wdyt @bmarty? If we can remove it, I'll handle it in a separate PR.