[Copilot]

CI demo artifact builds could succeed while packaging base-template code when a demo intentionally referenced sample files from a sibling demo directory. This change aligns build inputs with markdown cross-demo includes so generated APK/IPA artifacts reflect documented samples.

• Android workflow: shared-input fallback

  • In build-android-demos.yml, added markdown-include parsing for ../MASTG-DEMO-*/... references.
  • Added source resolution logic for build inputs (MastgTest.kt, AndroidManifest.xml, XML configs, ProGuard rules, etc.): prefer local demo file, otherwise load from referenced sibling demo directories.

• iOS workflow: shared-input fallback + checkout scope

  • In build-ios-demos.yml, expanded sparse checkout to demos/ios so sibling-referenced files are available during build.
  • Added the same reference parsing + fallback resolution for MastgTest.swift, Info.plist, and MASTestApp.entitlements (wired through EXTRA_ENTITLEMENTS).

• Behavioral contract

  • Local demo files remain highest priority.
  • Cross-demo files are only used when local equivalents are missing.
  • Existing demos without cross references continue to build unchanged.

# Conceptual resolution order now used by both workflows:
resolve_source_file "<file>" {
  1) "$demo/<file>"
  2) "<each ../MASTG-DEMO-* referenced in demo markdown>/<file>"
}

• Fixes [Bug] CI builds omit shared sample files and publish default app templates for multiple Android and iOS demos #3980