Fix autosend when using unsupported auto-send values

[seadowg]

Closes #6203

This makes the auto-send attribute behaviour (mostly) consistent with older versions. It works as described in the spec, with two additions:

• Unsupported values (like "bubblegum", "desktop", "agent dale cooper" etc) are all treated as if there is no auto-send attribute and forms will be auto sent based on the setting in Collect. It's likely that people have been using "default" thinking that this means something, but it doesn't.
• The supported values work if the case is wrong ("True" or "tRue" for example) and if they have extra whitespace (" true" for example).

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

The biggest change here was to introduce a three element enum to try and make this less confusing. The auto-send attribute isn't really a "true" or "false" system - it's a "true" or "false" or "undefined" and to add to that "true" and "false" aren't really opposites. I think going with "forced", "opt-out" and "neutral" is more descriptive.

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?

Nothing has changed except for auto send, but it's always a bit of a minefield due to the fact it has both a setting and a form attribute. I think waiting for a behaviour verified tag before merging would be good here.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• 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

[lognaturel]

Really like the naming. 👍

[dbemke]

Tested with Success!

Verified on a device with Android 10

Verified Cases:

• issue A form is finalized (not sent) if there is "default" auto send setting in the form #6203 doesn't occur
• forms with auto send setting set to true (with capital letters or whitespace), false, default, random letters
• different auto send options set in Collect
• regression checks in auto send

[srujner]

Tested with Success!

Verified on a device with Android 13