tree 148ccb8ef173a848f66289dd25a9ac3fa36dad15
parent 0a9e9b22bb8e11f70cf03b29742b2362fca091bc
author Andrei Litvin <andy314@gmail.com> 1668697892 +0100
committer GitHub <noreply@github.com> 1668697892 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjdk8kCRBK7hj4Ov3rIwAAslMIAF2HK5e9rRtg3dPzCjT1IxCE
 mQoP0uIEPH6j6Y+QOkNsWTfrLQ+0Qzn+G9tQ/8fz3RXzk1sT+aQTOxnGaR1MZoFG
 UfbCHm+2zDFJ3xkgd4WklSjksJ45DZ+zuOUwYMOAk6xHte9IkgxHZtNyR8JlMBQg
 63dOpeqjBAqwRnT8Bm/7iHbC6akloPdoxhOPgG138fpUI4iGGk693/0tO1NkH644
 fIkJfcyB78Hq/0nEDGaxVTzFO3RQddm5Pzjb3WJlo9/7pvM/9XONbucGHMFZb+PV
 ko9fibB+Vr1wJ8kJzCud614EERTB9LoJnvLbtMI6GNWREz6s3Vjwr1bvdQkcYzU=
 =Sg+G
 -----END PGP SIGNATURE-----
 

Install zap v2022.11.16 in Docker images. (#23643)

* Install zap v2022.11.16 in Docker images.

Installing from a zip file since deb installation seems to add
an entire XWindows dependency and based on feedback from zap
folks the zip file is the one more tested.

* Fix moved line

* Only keep zap-cli in the image. zap is a UI tool, not used and quite large

* Remove node install: zap should be a stand-alone tool

* Remove chip-build-zap because this image is not compatible anymore with missing node.js installation from the base image

* Remove chip-build-zap from chip-build-vscode

* Remove zap image build attempts from CI