Allow strings.xml to contain plurals

[dewantawsif]

Closes #875

[ExNDY]

How it work on others targets? You doesnt add test cases for check your changes. Now it's cant be approved

[dewantawsif]

As explained in the linked issue the change only allows the generator to find plurals from strings.xml. The process is no different to extracting plurals from plurals.xml. The PR doesn't touch anything else to create a boarder effect.

[ExNDY]

The fact that mixed value resources are conventional in Android does not make that convention appropriate for the platform-neutral moko-resources input format. commonMain/moko-resources is not Android’s res/values.
findPluralNodes() is a node selector, not a guardrail. Expanding the filter makes the same physical file an implicit input to multiple independent generators, without duplicate detection, precedence rules, or validation when the same plural is declared in both plurals*.xml and strings*.xml. Adding strings*.xml to one factory is an Android-specific special case that weakens the existing resource-type separation.

[dewantawsif]

The fact that mixed value resources are conventional in Android does not make that convention appropriate for the platform-neutral moko-resources input format. commonMain/moko-resources is not Android’s res/values.

I'm not aware of any standard for i18n in JS or Wasm so can't comment on that but both Apple Platform and JVM has the same convention.

Apple Platforms: https://developer.apple.com/documentation/xcode/localizing-and-varying-text-with-a-string-catalog#Add-variants-for-strings-that-contain-plurals
JVM: https://docs.oracle.com/javase/8/docs/api/java/text/ChoiceFormat.html with https://docs.oracle.com/javase/8/docs/api/java/util/ResourceBundle.html

findPluralNodes() is a node selector, not a guardrail. Expanding the filter makes the same physical file an implicit input to multiple independent generators, without duplicate detection, precedence rules, or validation when the same plural is declared in both plurals*.xml and strings*.xml.

The same is true when a single plurals*.xml file has duplicates.

Adding strings*.xml to one factory is an Android-specific special case that weakens the existing resource-type separation.

Would having it be a opt-in option suffice?