Fix autoCapitalize bitmask collision with numeric inputType flags

[lukeharvey]

Summary:

setAutoCapitalize applies AUTOCAPITALIZE_FLAGS (0x7000) to all input types, but this mask overlaps TYPE_NUMBER_FLAG_SIGNED (0x1000) and TYPE_NUMBER_FLAG_DECIMAL (0x2000). On every Fabric re-render, this strips the signed/decimal flags from numeric inputs, causing commitStagedInputType to call setInputType() with corrupted flags, which restarts the IME and breaks composing-based input (e.g. Samsung keyboards' shared ./- key).

The fix skips setAutoCapitalize for TYPE_CLASS_NUMBER inputs, where autocapitalize is meaningless.

Changelog:

[Android] [Fixed] - Fix setAutoCapitalize stripping numeric TextInput flags (TYPE_NUMBER_FLAG_SIGNED/DECIMAL), affecting minus sign input on Samsung keyboards

Test Plan:

A unit test was added to ReactTextInputPropertyTest.kt that verifies setAutoCapitalize does not strip TYPE_NUMBER_FLAG_SIGNED or TYPE_NUMBER_FLAG_DECIMAL when the input type class is TYPE_CLASS_NUMBER.

[meta-cla]

Hi @lukeharvey!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[NickGerleman]

Fix makes sense to me, but I think we would need to re-run this logic if keyboard type changes as well?

Maybe we can derive correct final InputType, from the different props onAfterUpdateTransaction().