Implement Docker best practices on ESP32 image

[electrocucaracha]

Problem

Previous attempt to reduce the image size and implement Docker best practices occurred when cryptography module was released. This python module doesn't allow to loading of X.509 certificates with negative serial numbers. A fix has been submitted to Espressif IoT Development Framework but we need to keep a patch until it's available.

Change overview

This change implements Docker best practices validated with Hadolint tool which helps to reduce the size. It also contains a patch file which removes the invalid certificate.

Fixes #10123

Testing

It was created ESP32 and ESP32 QEMU images locally and use act to validate the execution.

[todo]

Remove this patch once espressif/esp-idf#7632 is available

connectedhomeip/integrations/docker/images/chip-build-esp32/Dockerfile

Lines 16 to 26 in e17daa5

	# TODO: Remove this patch once https://github.com/espressif/esp-idf/pull/7632 is available
	COPY 0001-esp_crt_bundle-remove-EC-ACC-certificate.patch /tmp/esp-idf/0001-esp_crt_bundle-remove-EC-ACC-certificate.patch
	WORKDIR /tmp/esp-idf
	RUN set -x \
	&& git apply /tmp/esp-idf/0001-esp_crt_bundle-remove-EC-ACC-certificate.patch \
	&& rm -f /tmp/esp-idf/0001-esp_crt_bundle-remove-EC-ACC-certificate.patch \
	&& : # last line
	FROM connectedhomeip/chip-build:${VERSION}

---

This comment was generated by todo based on a TODO comment in e17daa5 in #10165. cc @electrocucaracha.

[bzbarsky-apple]

Ugh. I just realized that this had an undetected merge conflict: our docker version is already at 0.5.11. @andreilitvin @woody-apple Do we want to just do a standalone version bump, or revert this and reland with a version bump?