Android: Bump ndk/ndk-glue to 0.3 and use constants for event ident

[MarijnS95]

Following the changes in 1 this bumps ndk and ndk-glue to 0.3 and uses the new constants. The minor version has been bumped to prevent applications from running an older winit (without #1826) with a newer ndk/ndk-glue that does not pass this ident through the data pointer anymore.

• Tested on all platforms changed
• Compilation warnings were addressed
• cargo fmt has been run on this branch
• cargo doc builds successfully
• Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
• Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
• Created or updated an example program if it would help users understand this functionality
• Updated feature matrix, if new features were added or implemented

[MarijnS95]

CC @msiglreith

[MarijnS95]

   Uploading winit v0.24.0 (/home/runner/work/winit/winit)
error: api errors (status 200 OK): crate version `0.24.0` is already uploaded
Error: Process completed with exit code 101.

Has cargo publish always done this?

[msiglreith]

Yes, it just checks if the cargo toml changed and then tries to publish

[MarijnS95]

Yes, it just checks if the cargo toml changed and then tries to publish

@msiglreith Yes, but only few merges to master cause Publish to run and subsequently get a completely unnecessary build failure. Why is it running for this PR but not others?