Maul Window 0.12.0

A clipboard read's payload tied to its read, from an API audit after
0.11.0, keep rules for Android applications that shrink their code, and
touch exploration of a root that only has Explorer's method.

Added

• Android: java/proguard-rules.pro, what an application that shrinks its code with R8 or ProGuard must keep: the library's Java classes and members, which the native library finds by name, and a root's public virtualViewAt, found by reflection. The test applications are now built with R8 and these rules (mwin-0041).

Changed

• mwinGetClipboardText, mwinGetClipboardData and mwinGetPrimaryText take the read's request after the context, from its completion record, and answer mwin_errorStale for any request but a read answered done whose payload no later read replaced; before, a read could be answered with another window's read, or a superseded read's late bytes. Pass event.data.completion.request (mwin-0040).
• mwinRequestClipboardWriteData takes its item count as uint32_t, as the other requests with arrays do.

Fixed

• Android: touch exploration finds the node under the finger in a root that has a public int virtualViewAt(float x, float y) but does not implement maul.window.Explorer, as a provider of another library (Maul UI's) cannot; the library took such a root's hovers and announced nothing.