i18n: Make property paths and categories translatable

[timothyqiu]

master version of #58634

They are basically the same except master supports plural message and optional message context, so I modified the regex.

godot/editor/translations/extract.py

Lines 66 to 82 in d6df2ff

	# Regex "(?P<name>(?:[^"\\]|\\.)*)" creates a group named `name` that matches a string.
	message_patterns = {
	re.compile(r'RTR\("(?P<message>(?:[^"\\]|\\.)*)"(?:, "(?P<context>(?:[^"\\]|\\.)*)")?\)'): False,
	re.compile(r'TTR\("(?P<message>(?:[^"\\]|\\.)*)"(?:, "(?P<context>(?:[^"\\]|\\.)*)")?\)'): False,
	re.compile(r'TTRC\("(?P<message>(?:[^"\\]|\\.)*)"\)'): False,
	re.compile(
	r'TTRN\("(?P<message>(?:[^"\\]|\\.)*)", "(?P<plural_message>(?:[^"\\]|\\.)*)",[^,)]+?(?:, "(?P<context>(?:[^"\\]|\\.)*)")?\)'
	): False,
	re.compile(
	r'RTRN\("(?P<message>(?:[^"\\]|\\.)*)", "(?P<plural_message>(?:[^"\\]|\\.)*)",[^,)]+?(?:, "(?P<context>(?:[^"\\]|\\.)*)")?\)'
	): False,
	re.compile(r'_initial_set\("(?P<message>[^"]+?)",'): True,
	re.compile(r'GLOBAL_DEF(?:_RST)?\("(?P<message>[^".]+?)",'): True,
	re.compile(r'EDITOR_DEF(?:_RST)?\("(?P<message>[^"]+?)",'): True,
	re.compile(r'ADD_PROPERTY\(PropertyInfo\(Variant::[A-Z]+,\s*"(?P<message>[^"]+?)",'): True,
	re.compile(r'ADD_GROUP\("(?P<message>[^"]+?)",'): False,
	}

Seems a bit long and messy because I gave each capture group an explicit name (?P<name>expression) so it's easier to handle plural message and optional message context.

Tested message extraction without the property path patterns. The result is the same as the original approach except for one message which is fixed in #58705.

[akien-mga]

Thanks!