docs: Correct ADC default resolution statement for ESP32-S2

[eMUQI]

Description of Change

This PR corrects the documentation for analogReadResolution by removing an incorrect statement that the ESP32-S3 default ADC resolution is 13 bits.

As confirmed by the function's own documentation in the core header file esp32-hal-adc.h, the default resolution for analogRead is 12 bits (producing a range of 0-4095).

Tests scenarios

Compiled and run on Seeed Studio XIAO ESP32S3 in version v3.3.0. By running the standard AnalogReadSerial example code, confirmed that the default output range is 0-4095, corresponding to 12-bit resolution.

Related links

https://docs.espressif.com/projects/arduino-esp32/en/latest/api/adc.html#analogreadresolution

arduino-esp32/cores/esp32/esp32-hal-adc.h

Lines 49 to 56 in c7520cc

	/*
	* Set the resolution of analogRead return values. Default is 12 bits (range from 0 to 4096).
	* If between 9 and 12, it will equal the set hardware resolution, else value will be shifted.
	* Range is 1 - 16
	*
	* Note: compatibility with Arduino SAM
	*/
	void analogReadResolution(uint8_t bits);

https://github.com/espressif/esp-idf/blob/346870a3044010f2018be0ef3b86ba650251c655/components/soc/esp32s3/include/soc/soc_caps.h#L129-L130

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello eMUQI, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 6cc7a63

[P-R-O-C-H-Y]

Hi @eMUQI, I have checked the code and you are right about the S3. The documentation should say that for S2! Can you please instead of removing it change the S3 to S2? Thanks

[eMUQI]

Hi @P-R-O-C-H-Y , thanks for the review and clarification!
I've updated the PR as you suggested. Could you please take another look?