android-project: declare Quest passthrough feature and boundary visib…

…ility permission

The Quest OpenXR runtime hides XR_FB_passthrough from extension
enumeration without the com.oculus.feature.PASSTHROUGH uses-feature,
and XR_META_boundary_visibility without the
com.oculus.permission.BOUNDARY_VISIBILITY uses-permission (it logs the
missing strings under the OpenXR_Properties tag). Declare both in the
quest flavor manifest so the erhe editor can show camera passthrough on
its init status screen and suppress the boundary while passthrough is
visible (erhe issue libsdl-org#214). The feature is not required: the editor
falls back to a plain VR init screen without it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

android-project: add quest flavor manifest and hwasan wrap script

The quest flavor manifest replaces the activity element so the
MAIN+LAUNCHER+com.oculus.intent.category.VR categories share one
intent-filter (required for Horizon to treat the app as immersive VR),
declares headtracking, OpenXR loader broker permissions/queries, and
the supported Meta device list. wrap.sh enables HWASan runs; the
nested .gitattributes pins it to LF so the on-device shebang survives
Windows checkouts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

android-project: add quest flavor manifest and hwasan wrap script

The quest flavor manifest replaces the activity element so the
MAIN+LAUNCHER+com.oculus.intent.category.VR categories share one
intent-filter (required for Horizon to treat the app as immersive VR),
declares headtracking, OpenXR loader broker permissions/queries, and
the supported Meta device list. wrap.sh enables HWASan runs; the
nested .gitattributes pins it to LF so the on-device shebang survives
Windows checkouts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>