fix: Support patching on ARMv7 by updating AAPT2

[oSumAtrIX]

Binary taken from run https://github.com/ReVanced/aapt2/actions/runs/9977958347

[kitadai31]

Now that all architectures are fully supported, I think the entire architecture warning can be removed

revanced-manager/app/src/main/java/app/revanced/manager/ui/screen/DashboardScreen.kt

Lines 210 to 219 in 52a89b1

	if (!Aapt.supportsDevice()) {
	{
	NotificationCard(
	isWarning = true,
	icon = Icons.Outlined.WarningAmber,
	text = stringResource(R.string.unsupported_architecture_warning),
	onDismiss = null
	)
	}
	} else null,

revanced-manager/app/src/main/java/app/revanced/manager/patcher/aapt/Aapt.kt

Lines 7 to 9 in 52a89b1

	private val WORKING_ABIS = setOf("arm64-v8a", "x86", "x86_64")
	fun supportsDevice() = (DEVICE_ABIS intersect WORKING_ABIS).isNotEmpty()

[oSumAtrIX]

That's not all architectures

[kitadai31]

If you are talking about armeabi, mips and mips64, there is no need to consider them
If the device only supports those architectures, the installation will be rejected with a compatibility error because the package installer checks the apk archs

In addition, wasn't this warning necessary because armv7 aapt2 was unstable but still existed?
Previously, some ARMv7 devices were compiling resources successfully, and others were failing with 135 error
I believe this is the reason of the word "will most likely fail."
OTOH armeabi, mips and mips64 of aapt2 are not present in manager
This is the difference

[kitadai31]

I believe this is the reason of the word "will most likely fail."

nvm, I forgot about if users patched non-resource patches only

[oSumAtrIX]

The code can be kept as a pessimistic precaution. Its formely known as defensive programming