Request to ignore battery optimizations before receiving subscription

[p1gp1g]

This privilege is required to start a foreground service from the background. Which is what is intended to be done when the first registration is received with UnifiedPush

Fix #95

[p1gp1g]

By the way, I've added the possibility to change the battery settings without asking the user to do it manually in settings

I can split the PR if you prefer

[p1gp1g]

I see many users struggling with errors 507. This issue should fix it.

It happens because channels are created by the client, but because it isn't allowed to run in the background without restriction, it can't start a new foreground service, and so it can't register the new topic on the server. The new endpoint is still sent to the application. And we end with a 507 error.

Examples:

• Update UnifiedPush library element-hq/element-x-android#4358 (comment)
• No notifications and Error: HTTP 507 on Test Push loop back element-hq/element-x-android#4702

[binwiederhier]

I plan to release Android after the ntfy server. I'll look at all the PRs then!

[p1gp1g]

Great news !

The last comment was to add some context, I tend to forget to include it in my PRs and I saw I forget to mention the 507

[NextWork123]

I plan to release Android after the ntfy server. I'll look at all the PRs then!

Some news about that?

[binwiederhier]

Very cool. It opens a neat confirm dialog. Thanks