Fixes #16797.  Commit new CLDR v22.1 core.zip and default ant build output.
Put touch click normalization in dojo/touch, rather than in dijit/a11yclick and various mobile modules.   Unlike the old dijit/a11yclick code, the new code works by squelching the real click event, and instead always generating a synthetic click event.   Limited to nodes that have a dojoClick property set, or an ancestor with the dojoClick property set.  Patch from Eric Durocher (IBM, CCLA), fixes #15878 !strict.

Some dijit widgets like dijit/Tree and dijit/!TitlePane are currently manually listening for click events and keyboard events; they need to be updated to set the dojoClick property on their nodes instead.
fix regression from [28465] where errors don't get reported, fixes #16813 and refs #15118, #14591 on trunk/, thanks Jared, !strict.
Fix _WidgetsInTemplateMixin to not parse widgets inside of this.containerNode (except if this.searchContainerNode is set to true).   Refs #16576 !strict.
repair improper test assert; thanks jonathansampson; fixes #15771
repair improper test assert; thanks jonathansampson; fixes #15774
repair improper test assert; thanks jonathansampson; fixes #15775; refs #15774, #15771
Suppress mousedown and mouseup events that occur 300ms after the synthetic click event is fired, since they may confuse client code.   Also, do a better job of suppressing the native click event that (may) occur 300ms after the synthetic one; it sometimes appears on the DOMNode behind a popup that was closed in the 300ms interval.   Patch from Eric Durocher (IBM, CCLA).

Refs #15878 !strict.
Make !BorderContainer splitters wider on iOS and android, so that they can be easily grabbed.   Didn't adjust the !BorderContainer padding or gutter size to match; maybe I should, to be consistent, but the other issue with mobile is limited screen space.   Fixes #16831.

Also adding .dj_ios and .dj_android CSS flags to uacss.js.
Don't call preventDefault() on the native click event, otherwise on Android text fields cannot be edited anymore.  Not sure why, since we are generating a synthetic click event.   Similarly, not sure why this doesn't break (native) checkboxes.   Seems like they would be getting two clicks now instead of one.   But, everything seems to work with this change.  Refs #15878 !strict.
Merge remote-tracking branch 'upstream/master' into custom2