Compile android in build_examples.py and move android compilation outside of Github CI

[andy31415]

Problem

Android chiptool example is not built by build_examples.py

Change overview

Add android libraries and App support in build_examples.py
Disable Github Action for 'android.yaml' and leave it to run in GCP only

Testing

Ran compilation manually in vscode environment
Unit test
GCP CI will run this.

[andy31415]

vscode does not seem to allow license accepting. This will only pass after #8864

[mspang]

Please don't use directory listings in build scripts.

[mspang]

Please don't use directory listings in build scripts.

(very few build systems delete files, they only replace them. Doing this invariably leads to broken outputs and confused engineers)

[github-actions]

Size increase report for "gn_qpg-example-build" from 2ee1e70

File	Section	File	VM
chip-qpg6100-lighting-example.out	.text	-16	-16

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-qpg6100-lighting-example.out.map and ./pull_artifact/chip-qpg6100-lighting-example.out.map:

BLOAT EXECUTION FAILED WITH CODE 1:
bloaty: unknown file type for file './pull_artifact/chip-qpg6100-lighting-example.out.map'

Comparing ./master_artifact/chip-qpg6100-lighting-example.out and ./pull_artifact/chip-qpg6100-lighting-example.out:

sections,vmsize,filesize
[Unmapped],0,16
.debug_ranges,0,8
.debug_str,0,1
.debug_loc,0,-5
.text,-16,-16
.debug_line,0,-25
.debug_info,0,-43

[github-actions]

Size increase report for "esp32-example-build" from 2ee1e70

File	Section	File	VM
chip-lock-app.elf	.flash.text	68	68
chip-all-clusters-app.elf	.flash.text	-8	-8

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-bridge-app.elf and ./pull_artifact/chip-bridge-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-shell.elf and ./pull_artifact/chip-shell.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-lock-app.elf and ./pull_artifact/chip-lock-app.elf:

sections,vmsize,filesize
.flash.text,68,68
[Unmapped],0,-68

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize
[Unmapped],0,8
.riscv.attributes,0,-2
.debug_info,0,-8
.flash.text,-8,-8
.debug_ranges,0,-16
.debug_loc,0,-48
.debug_line,0,-50

Comparing ./master_artifact/chip-persistent-storage.elf and ./pull_artifact/chip-persistent-storage.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-ipv6only-app.elf and ./pull_artifact/chip-ipv6only-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-temperature-measurement-app.elf and ./pull_artifact/chip-temperature-measurement-app.elf:

sections,vmsize,filesize

[andy31415]

Please don't use directory listings in build scripts.

(very few build systems delete files, they only replace them. Doing this invariably leads to broken outputs and confused engineers)

Updated to not use rsync/path walk equivalents.
Unfortunately the 'copy to source' is still needed for gradle and cound not remove it in this PR. sideffect is that the APK instead of supporting only one platform, would 'support' everything that gets copied into jnilibs.

[mspang]

Please don't use directory listings in build scripts.

(very few build systems delete files, they only replace them. Doing this invariably leads to broken outputs and confused engineers)

Updated to not use rsync/path walk equivalents.
Unfortunately the 'copy to source' is still needed for gradle and cound not remove it in this PR. sideffect is that the APK instead of supporting only one platform, would 'support' everything that gets copied into jnilibs.

Ok, that's broken, and is exactly the kind of unfortunate issue that globbing causes.