Upgrade JavaRosa

[seadowg]

Closes #4554

This upgrades JavaRosa so that instance files are now encoded as UTF-8 (rather than ASCII with escaped characters). Unicode will now be unescaped in instance XML and there is an encoding attribute added to the XML doc itself.

What has been done to verify that this works as intended?

Ran existing tests and verified that forms now included unicode manually (there are tests on the JavaRosa side for this).

Why is this the best possible solution? Were any other approaches considered?

Discussion at getodk/javarosa#685.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

It would be good to do a general pass on saving/submitting forms with emoji or other unicode.

Before submitting this PR, please make sure you have:

• run ./gradlew checkAll and confirmed all checks still pass OR confirm CircleCI build passes and run ./gradlew connectedDebugAndroidTest locally.
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[srujner]

Tested with Success!
Verified on Androids: 10, 11 and 12

Verified Cases:

• Saving Forms;
• Sending finalized Forms to the Central;
• Editing saved Forms;
• Regression check on forms with Text widgets, sending emojis and other Unicode symbols;
• Hierarchy view

[seadowg]

@srujner should this be behavior verified now?

[srujner]

@seadowg We are only waiting for @kkrawczyk123 to check this also on Android 5.1

[kkrawczyk123]

Tested also on Androids 5.1 and 8.1.