Update our workflows to the new latest docker builds as well fix nRF builds

[woody-apple]

Problem

Our docker builds are... a few builds back, and when I went to update things - some stuff seems to not be working.

Summary of Changes

• Updated the nRF paths, Fixes: nRF Docker image doesn't build #4655
• Updated the docker builds to latest (for now, working on proper Docker build image CI)
• Rebuilt all docker images based with no changes (except nRF paths) - packages would be updated, but nothing else

Help needed

• For some reason some DNS tests are failing, though all accessory builds work just fine, including QEMU
• Main builds fail (same as above) - weird, we seem to be running the same jobs twice...
• Cirque tests fail (possible same as above)

[woody-apple]

@andy31415 @jelderton @saurabhst @bzbarsky-apple

Ready for review (Note, will be following up about the "latest" tag in: #3411)

Also filed:
#4658
#4659

[github-actions]

Size increase report for "esp32-example-build" from 26061f6

File	Section	File	VM
chip-all-clusters-app.elf	.iram0.text	1068	1068
chip-all-clusters-app.elf	.dram0.data	-96	-96
chip-all-clusters-app.elf	.dram0.bss	0	-2064
chip-all-clusters-app.elf	.flash.text	-2804	-2804
chip-all-clusters-app.elf	.flash.rodata	-5856	-5856

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

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

sections,vmsize,filesize
.debug_info,0,40586
.debug_str,0,4310
.debug_line,0,2334
.debug_abbrev,0,1516
.debug_ranges,0,1232
.strtab,0,1078
.iram0.text,1068,1068
.debug_frame,0,1000
[Unmapped],0,788
.symtab,0,672
.debug_aranges,0,328
.shstrtab,0,-34
.xt.prop._ZN14NVSHandleEntryD2Ev,0,-76
.dram0.data,-96,-96
.debug_loc,0,-1946
.dram0.bss,-2064,0
.flash.text,-2804,-2804
.flash.rodata,-5856,-5856

[andy31415]

One worry in using ':latest' is that it will couple docker releases with builds.

Currently if I build on version A and need a breaking change to build with B (e.g. a SDK update that requires code changes for compatibility), currently I can have:

• PR to update docker to B. Code uses A still.
• upload new docker (now both A and B are in docker)
• PR to update code to B and use image B.

Throughout I would have no CI breakages because code specifies with what image it is compatible.

If code uses ":latest" I am unsure how the label should be updated since as soon as I change the label, all code would use the updated image.

@woody-apple - thoughts? Are the benefits of not needing to keep updating versions better than the downside of not being able to push incompatible SDK versions (and some non-reproducible builds, since checking out old commits may still use new SDKs) ?

[woody-apple]

One worry in using ':latest' is that it will couple docker releases with builds.

Currently if I build on version A and need a breaking change to build with B (e.g. a SDK update that requires code changes for compatibility), currently I can have:

• PR to update docker to B. Code uses A still.
• upload new docker (now both A and B are in docker)
• PR to update code to B and use image B.

Throughout I would have no CI breakages because code specifies with what image it is compatible.

If code uses ":latest" I am unsure how the label should be updated since as soon as I change the label, all code would use the updated image.

@woody-apple - thoughts? Are the benefits of not needing to keep updating versions better than the downside of not being able to push incompatible SDK versions (and some non-reproducible builds, since checking out old commits may still use new SDKs) ?

As mentioned above, this is temporary - I'm working on our proper docker CI, and this will at least keep our builds more up to date (some of the old workflows were vastly out of date).

For the mean time, I'll keep an eye on docker images, and plan on getting our CI up either this week or weekend. I also have a pipeline I'm testing to rev all the version numbers in source when we push.

[woody-apple]

I hate to pile on, but this is resolved here too:
#4670

[woody-apple]

@saurabhst ?

[woody-apple]

Merging due to hot-fix, due to broken build