Bump to 4.4.1: OpenSSL privacy manifest for iOS _ssl/_hashlib

[FeodorFitsner]

Re-pins the bundled python-build snapshot to 20260726 and bumps all six packages to 4.4.1.

What's in the snapshot

flet-dev/python-build#35 only — the PrivacyInfo.xcprivacy bundled into _ssl.framework and _hashlib.framework was a stub (NSPrivacyAccessedAPITypes empty, plus an NSPrivacyUsesNonStandardAPIs key that isn't in Apple's schema). It's now byte-identical to OpenSSL's official manifest, declaring the file-timestamp API access the library actually performs.

No versions moved — Python 3.12.13 / 3.13.14 / 3.14.6, Pyodide, and dart_bridge 1.6.1 are all unchanged from 20260725. The manifest is the only functional difference on any platform.

Note the changelogs avoid the "byte-identical to the previous snapshot" phrasing used in prior bumps: all 31 release assets differ in size between 20260725 and 20260726, so every platform was rebuilt. They're functionally unchanged, not byte-identical.

What this does not fix

flet-dev/flet#6724 — ITMS-91065: Missing signature on a first App Store submission, citing these same two frameworks. This change is not expected to resolve it and shouldn't be announced as the fix.

Apple emits no ITMS-91061 alongside that rejection, so it does find the manifest. Inspecting a built .ipa ruled out every signature-side explanation:

Hypothesis	Finding
Framework ships unsigned in the IPA	Signed — valid authority, correct TeamIdentifier
A vendor signature applied in python-build would survive	No — codesign -f at both the embed step and exportArchive; 120 invocations covering all 118 frameworks, overwriting even Google's signature on Flutter.framework
Privacy manifest absent	Present, plutil clean
Manifest not sealed by the signature	Sealed — in both files and files2 of _CodeSignature/CodeResources

So the framework reaches Apple signed, with a sealed manifest, and is still reported as unsigned. This PR removes the one verifiable defect so it isn't a confound in further testing.

Verification

• gen_version_tables --release-date 20260726 regenerated all five tables; the no-arg re-run produces no further diff (matches the CI "Version tables in sync with manifest" check).
• Only the release date moved in the generated files — no version fields changed.
• No stale 4.4.0 left in any pubspec, build.gradle.kts, or podspec.

Not tagged, not published.