Support for AXP2101 Single Cell NVDC PMU with E-gauge

**Describe the problem you have/What new integration you would like**

Add support for AXP2101 Single Cell NVDC PMU with E-gauge for [M5Stack devices](https://shop.m5stack.com/pages/search-results-page?q=AXP2101).

| CHIP | AXP2101 | Remarks |
| ---------- | -------------------------------------- | ---------------- |
| DC1 | 1.5-3.4V /2A | |
| DC2 | 0.5-1.2V,1.22-1.54V /2A | |
| DC3 | 0.5-1.2V,1.22-1.54V,1.6-3.4V /2A | |
| DC4 | 0.5-1.2V,1.22-1.84V /1.5A | |
| DC5 | 1.2V,1.4-3.7V /1A | |
| LDO1(VRTC) | 1.8V /30mA | |
| LDO2 | x | |
| LDO3 | x | |
| LDO4 | 1.8V-3.3V /200mA | x | |
| LDO5/IO0 | 1.8-3.3V /50mA | x | |
| ALDO1 | x | 0.5-3.5V /300mA | |
| ALDO2 | x | 0.5-3.5V /300mA | |
| ALDO3 | x | 0.5-3.5V /300mA | |
| ALDO4 | x | 0.5-3.5V /300mA | |
| BLDO1 | x | 0.5-3.5V /300mA | |
| BLDO2 | x | 0.5-3.5V /300mA | |
| DLDO1 | x | 0.5-3.3V/ 0.5-1.4V /300mA | |
| DLDO1 | x | 0.5-3.3V/ 0.5-1.4V /300mA | |
| CPUSLDO | x | 0.5-1.4V /30mA | Dependent on DC4 |

**Please describe your use case for this integration and alternatives you've tried:**

- [M5Stack Core2 v1.1](https://shop.m5stack.com/products/m5stack-core2-esp32-iot-development-kit-v1-1)
- [M5Stack CoreS3](https://shop.m5stack.com/products/m5stack-cores3-esp32s3-lotdevelopment-kit)

**Additional context**

- Datasheet
* [AXP2101_Datasheet_V1.0_en.pdf](AXP2101_Datasheet_V1.0_en.pdf)
- Arduino lib
* [XPowersLib AXP2101_Voltage_Example ](https://github.com/lewisxhe/XPowersLib/tree/master/examples/AXP2101_Voltage_Example)
* [M5Unified AXP2101 class](https://github.com/m5stack/M5Unified/blob/master/src/utility/AXP2101_Class.cpp)

Read the AXP2101 datasheet and compare the XPowersLib AXP2101_Voltage_Example with M5Unified's AXP2101_Class.cpp. Then determine the ESPHome integration entry point for the M5Stack Core2 v1.1 and CoreS3, and define the requested PMU and E-gauge support. Done means both devices can use the requested AXP2101 functionality.

Written by the indexing model from the issue text.