Android: Properly validate godot_project_name_string for Android special chars

[akien-mga]

Fixes #52659.

This true enabled p_escape_quotes in xml_escape:

godot/core/string/ustring.cpp

Lines 3876 to 3884 in f2cf52e

	String String::xml_escape(bool p_escape_quotes) const {
	String str = *this;
	str = str.replace("&", "&");
	str = str.replace("<", "&lt;");
	str = str.replace(">", "&gt;");
	if (p_escape_quotes) {
	str = str.replace("'", "&apos;");
	str = str.replace("\"", "&quot;");
	}

And apparently that caused issues.

That's not it, see #54255 (comment).

It was added like this originally by @amanj120 in #42185 as part of implementing Android App Bundle support.

[akien-mga]

So this needs more work, there's actually a full table of characters that need to be escaped but not using standard XML escapes... :|
https://developer.android.com/guide/topics/resources/string-resource.html#FormattingAndStyling

[akien-mga]

This now does the full escaping magic, aside from handling U+XXXX unicode codes. I'm not sure that's something we support for the Android package name in the first place so I didn't bother. Could be implemented later on if there's a need for it though.

Tested with:

[application]

config/name="Do's and
\"Some\"        t@b?
 Don'ts"

Generates:

<?xml version="1.0" encoding="utf-8"?>
<!--WARNING: THIS FILE WILL BE OVERWRITTEN AT BUILD TIME-->
<resources>
        <string name="godot_project_name_string">Do\'s and\n\"Some\"\tt\@b\?\n Don\'ts</string>
</resources>

And works fine too on device:

Also to note, I used xml_escape(false) since we already escape the quotes for Android's purpose and they're otherwise valid in the XML. But it wouldn't be wrong either to also escape them to XML codes, Android docs mention that both are supported (so it should still detect \' as an Android-escaped single quote).

[akien-mga]

This now does the full escaping magic, aside from handling U+XXXX unicode codes. I'm not sure that's something we support for the Android package name in the first place so I didn't bother. Could be implemented later on if there's a need for it though.

I just tested to be sure, using e.g. U+2013 in a project name does not trigger an error. It's just handled as a simple string, not as a unicode codepoint.

[akien-mga]

Cherry-picked for 3.4.