Improvements to passkey support: * Changed how Private Key data is stored in the entries. This fixes issues e.g. on Discord Web and improves compatibility with KeepassXC * Made CredentialID, PrivateKey and UserHandle fields protected * changes BE/BS flags to 0/1 instead of false/true for compatibility with other tools * removed the "passkey:" prefix in the URL field * when searching for passkey, KP2A now correctly searches the KPEX_PASSKEY_RELYING_PARTY fields instead of URL * fixes calculation of clientDataHash and origin-id extraction, fixing issues with non-browser based usage.

It's ridiculous... Google Play suddenly decided that this app "collects personal data" but doesn't declare this on Google Play. Their definition is clear - only data transmitted to the developer or third parties is relevant and that is obviously not the case for Keepass2Android. Anyway, they refuse to accept updates, even after an appeal. They present "proof" by a screenshot of adding an entry based on the E-mail template. So what should I do? Only bad options... I removed that template for new databases 🤷‍♂️

Removed donation button in about dialog and link to plugins wiki page.

Improvements to URL handling for WebDav with non-ASCII characters (#3030)

added more Oktoberfest dates :-)

## What's Changed * Stability improvements * Attempt to fix issue with OneDrive AppFolder

## What's Changed * Update to .net 9 and Target SDK version 35. This comes with changes in the UI because of edge-to-edge as default. * Smaller UI improvements (credential dialogs, don't show delete-entry menu when viewing history elements) ### Online-version only: * Update Jsch

In addition to [v1.13-r0](https://github.com/PhilippC/keepass2android/releases/tag/v1.13-r0): * add option to disable QuickUnlock blocking behavior * fix quickunlock layout