[Study] Identify if an Android/iOS archive has been built with OUDS Flutter

📋 Description

As an automated process running in the publication process
When a package is delivered for publication,
I want to be able to identify the Android or iOS archive that have been built with OUDS-Flutter (Orange Unified Design System)
So that it can be scanned by the publication tool and log that information in the tool.

🎯 Goal

Implement a mechanism to detect or certify that a mobile archive
(.apk, .ipa) has been built using OUDS-Flutter.

💡 Suggested approach

Create a detection script to be run as part of the OMA build,
which would:

• Inspect the archive content to find OUDS-related artifacts
  (e.g. resources, metadata, class names, dependencies)
• Check for the presence of a specific OUDS marker
  (e.g. a property in AndroidManifest.xml or Info.plist)
• Output a clear result indicating whether OUDS was used,
  and if possible, which version
• Optionally fail the build or raise a warning if OUDS is not detected

✅ Acceptance criteria

• A script is created and integrated into the OMA build pipeline
• The script works for both Android and iOS archives
• The script outputs a clear and readable result
• The solution is properly documented
• The OMA team can rely on this script during the delivery process