document microG access to mtalk and ANDroID.cliENTS

Summary

This is just a minor request for documentation as a disclaimer at https://esolutions.shop. If I'm wrong, let me know.

Description

Who will use the new feature?

Anyone interested in buying a degoogled phone.

What is the target of the new feature for this user?

To know that network access to google.com is needed, what is that network access and for what.

Why this user would like to use this feature?

I have a phone from efoundation and I expected no access to google servers (otherwise why buy a degoogled phone) but NetGuard reports access to mtalk.google.com and ANDroID.cliENTS.gOoGLE.COM from the microG Services Core. If this is needed, please mention it in your documentation, otherwise....degoogle it.

I have opened it also at: https://github.com/microg/GmsCore/issues/1508

Examples

"Make sure to put mtalk.google.com on your whitelist, or else problems are likely to occur when using Firebase Cloud Messaging."

or the following if it is true:

"We still need to access mtalk.google.com and ANDroID.cliENTS.gOoGLE.COM in order for push notifications to work"

Reflection

Validation

If the above makes sense, AB testing buyers could prove whether such documentation would be appreciated or not and whether it would be read or not depending on the placement.