ESP32-H2: add platform support for Thread end device

[wqx6]

Problem

Add platform support for Thread end device on ESP32-H2, the new BLE/15.4 combo SoC from Espressif.

Change overview

Add Thread stack in esp32 platform for our 15.4 chip ESP32-H2.

Testing

Test with ESP32-H2

1. BLE connection with python control.
2. Thread network provisioning

[chshu]

Please double verify that the change won't break any functionality of ESP32 and ESP32-C3 as Wi-Fi end devices.

[andy31415]

Please update the code to not #ifdef large amount of code. We had this in the system and inet layer and are suffering because of this.

[chshu]

Could you ensure example apps (at least some) compile on the new platform?

./scripts/build/build_examples.py should work (so I can test compilation from vscode).

@andy31415 The ESP32-H2 IDF branch for Matter is not public yet, this PR mainly aims to enable Espressif's Thread platform support, the ESP32-H2 examples will be supported later when its IDF branch is public.

By merging this PR, it helps to unblock our internal development process, that we can develop both Wi-Fi and Thread Matter devices software on the same code base.

[andy31415]

Could you ensure example apps (at least some) compile on the new platform?
./scripts/build/build_examples.py should work (so I can test compilation from vscode).

@andy31415 The ESP32-H2 IDF branch for Matter is not public yet, this PR mainly aims to enable Espressif's Thread platform support, the ESP32-H2 examples will be supported later when its IDF branch is public.

By merging this PR, it helps to unblock our internal development process, that we can develop both Wi-Fi and Thread Matter devices software on the same code base.

My take on this is that we deny any platforms/versions that cannot be compiled by CHIP developers and CI (if we desire) without any need of special configurations/separate downloads/signing NDAs or similar hurdles.

In this case, since this is an unreleased product, CHIP developers cannot compile it without having access to a private/restricted SDK build. This makes it unsuitable for mainline CHIP build. If you have access to some 'beta' SDK and can place that under the vscode (and/or esp32 version) we can reevaluate.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[woody-apple]

@andy31415 it looks like this compiles happily, but supports upcoming development.

@wqx6 can you fix the merge conflicts here?

[andy31415]

At some point we may want to make build_examples.py also support the new board type.

[github-actions]

Size increase report for "esp32-example-build" from 37a6d27

File	Section	File	VM
chip-all-clusters-app.elf	.flash.text	-20	-20

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,539
.debug_line,0,128
.strtab,0,105
.debug_loc,0,35
.debug_frame,0,24
[Unmapped],0,20
.debug_abbrev,0,18
.symtab,0,16
.debug_aranges,0,8
.debug_ranges,0,8
.debug_str,0,5
.riscv.attributes,0,3
.shstrtab,0,3
.flash.text,-20,-20