Block closing the notification permission dialog by tapping outside the bounds

[grzesiek2010]

Closes #5758

Why is this the best possible solution? Were any other approaches considered?

I think one way of closing the dialog (by clicking the ok button) is enough and we should block closing it by tapping outside the bounds.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

Testing the dialog should be enough. Other parts of the app should not be affected.

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew checkAll and confirmed all checks still pass OR confirm CircleCI build passes and run ./gradlew connectedDebugAndroidTest locally.
• added a comment above any new strings describing it for translators
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[srujner]

Tested with Success!

Verified on device with Android 13

Verified cases:

• issue Tapping outside notification permission description dialog dismisses it with no way to grant permission #5758 is no longer reproducing;
• Notification dialogs;
• Other dialogs in the app;
• Rotate the screen, minimize the app;
• Don't keep activities enabled/disabled.