upstream: bump version to v12.2.10

Long time no see!

We will stick with the old UI and this major version for a long time, until I find a stable way to merge upstream without switching to the new UI. The new UI is just too ugly; I don't like it.

The chat input bar is using the new UI. This was an oversight, but I don't have time to deal with it right now. I will revert it to the old UI later.

This version is an early release, as I haven't been tracking bugs for a while. I currently don't know the exact issues, though I may have a clue about one or two bugs. If you encounter any problems, please give your feedback.

For now, the short-term plan is to manually backport some of the interesting feature updates from newer upstream versions. Currently, I am quite interested in "member tag" and "recently visited chats".

Stay tuned.

Signed-off-by: qwq233 <qwq233@qwq2333.top>

fix network lagging
this issue is caused by obfuscation.
i was obviously using the unobfuscated version, so i didn't encounter this problem. sry for that.

Warning about unofficial apps was found in Telegram iOS translation_keys.

So, if a user is using an unofficial Telegram app, you will see a warning «%@ uses an unofficial Telegram client – messages to this user may be less secure».

@telelakel

Maybe some of you have heard the news.

First of all, Nullgram is not a fork of that rumored client.

Secondly, even if you are using any of its forks, you don't need to worry. The data collection code is located in the private codebase, so unless the client you are using added something similar (really?), there is nothing to worry about.

Finally, if you are using that rumored client right now, there's no need to worry either. Because your info has already been uploaded, and it's a bit too late to switch to another client now anyway.

Btw, if you are worried about whether Nullgram has similar security risks, you can audit the APK build process yourself. The hash of the APK file should be identical to the sha256 hash recorded in GitHub Actions.

When you use a third-party client, you have to take responsibility for your own data security. If you don't have the ability to audit code, then you are still basically using a closed-source client. So even if you use an open-source client, you still need to pay attention to this kind of issue.

support member tag experimentally

added experimental support for rich messages.
didn't push the related commits cuz it's still being tested.
pls report issues if anyone has any.

restore input bar ui style
fix some bugs with translate
pls report issues if anyone has any.
i will publish a stable version very soon.

# What's Changed

## Features:
- feat: add experimental group member tags, including member/admin/owner tags, editing permissions, and admin-log support
- feat: add a granular group permission for sending reactions
- feat: support rich messages with structured text and media, including math, tables, galleries, and audio
- feat: support next-generation polls with media and link attachments, participant-added options, revoting, deadlines, hidden results, voter restrictions, statistics, and a
dedicated shared-media tab
- feat: support admin-bot-managed join requests, including bot replacement, Web App approval, and result notifications
- feat: restore the classic early-11.x chat composer UI while preserving v12.2 functionality

## Fixes:
- fix(tcp2ws): refresh the TLS toggle state immediately after changes
- fix: ignore no-forward restrictions in TranslateAlert
- fix: prevent R8/ProGuard from stripping required zero-argument TL constructors
- fix: prevent a null-pointer crash when ChatActivityEnterView updates the Send As state without a parent fragment
- fix: correct TL parsing and related Story music file-reference and Star Gift rarity handling
- fix: stop completed in-message translations from being processed repeatedly

## Improvements:
- style: improve the position, color, and centering of profile ID text

## Chores:
- chore: update the Android build stack to AGP 9.3.0, Gradle 9.6.1, Kotlin 2.4.10, JGit 7.7.0, NDK 29, and target SDK 36
- chore: migrate fingerprint capability checks to AndroidX Biometric
- chore: temporarily disable Android's OnBackInvokedCallback API

## Major Update:
- upstream: bump Telegram Android from v11.13.0 to v12.2.10

those interested in live photo can try this and see if it works.
i don't use it so no idea if it works or not.
pls report with logs if it doesn't.
pls also report it works so i can push related commits