Implement SigmaDelta based on ESP-IDF API (espressif#6053)

Summary

This PR is refactoring of SigmaDelta HAL in order to use IDF instead of current Register manipulation approach.

Impact

Change in API:

uint32_t sigmaDeltaSetup(uint8_t channel, uint32_t freq);
changed to -->
uint32_t sigmaDeltaSetup(uint8_t pin, uint8_t channel, uint32_t freq);

void sigmaDeltaAttachPin(uint8_t pin); removed, no longer needed. Pin is attached in sigmaDeltaSetup()

Update package_esp32_index.template.json

Add ALPN support to WiFiClientSecure (espressif#5633)

This adds a function to WiFiClientSecure to set the ALPN protocol.

This is required for an MQTT client to connect to AWS IoT when using an AWS Custom Authorizer, as described here.

Example code snippet:

...
WiFiClientSecure wiFiClient;

// ALPN protocol, needed with AWS custom authorizer
const char *aws_protos[] = {"mqtt", NULL};

void setup() {
  wiFiClient.setCACert(AWSCAPEM);
  wiFiClient.setAlpnProtocols(aws_protos);
}
...

Added UM FeatherS2 Neo to boards.txt and added appropriate variants. (e…

…spressif#5615)

Implement USB HID Device Support for ESP32-S2 (espressif#5538)

* Add support and example for USB HID Devices
* Add support and example for USB Vendor

Fix Windows USB issues

- Device will not reset if previous baudrate was not 9600
- CDC Device is not recognized if WebUSB is enabled

IDF master cf457d412 (espressif#5073)

esp-dsp: master 7cc5073
esp-face: master 420fc7e
esp-rainmaker: f1b82c7
esp32-camera: master 2dded7c
esp_littlefs: master d268e18

Quote {build.source.path} to allow spaces in path (espressif#4868)

Previously sketches or examples that had spaces anywhere in their absolute
path caused a total build failure. By adding quotes around the path in
platform.txt, they now build correctly

Co-authored-by: Me No Dev <[email protected]>

etboard pinmap upload (espressif#4748)

Co-authored-by: ketri-kjy <[email protected]>
Co-authored-by: ketri2484 <[email protected]>

Improve cleanup in BLEClient (espressif#4742)

- Remove client from the list of devices in case registration fails
- Filter other events not related to registration during registration phase
- Cleanup if connect fails
- Reset if after disconnect
- Disconnect callback *after* cleanup is done so object can be deleted

This fixes some of the issues I had like:
- `BLEClient::connect` hangs up and never recovered because registration failed
- `BLEClient` could not be deleted after disconnect or deletion creating ghost events espressif#4047
- `BLEClient` could not be properly reused after a connection was attempted (successful or not) 

* Cleanup in case of registration and connect failure.
Cleanup before calling disconnect callback for safe delete.
Reject other events during registration.
Adresses espressif#4047, espressif#4055

* Clear if after unregister espressif#4047