ADC: Add async support for oneshot reads for esp32c3 and esp32c6

[davoclavo]

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

• I have updated existing examples or added new ones (if applicable).
• I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
• My changes were added to the CHANGELOG.md in the proper section.
• I have added necessary changes to user code to the Migration Guide.
• My changes are in accordance to the esp-rs API guidelines

Extra:

• I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖

Description

Add support for ADC async oneshot reads for esp32c3 and esp32c6. Fixes #1643

Testing

Added QA example that uses embassy executor and reads every second from GPIO5. I am able to measure distinct values just by handling the devkit board with my hands.

Extra notes

1. It seems the double oneshot read hack for esp32c6 is not required if interrupts are used. If someone is able to help me figure out a way to replicate the issue I could try to see if we need to add that hack back.

2. Not sure if this is critical, but I am unsure if its possible to perform concurrent reads to multiple channels using the same ADC interface, in order to address the potential issue that is currently solved by using the active_channel attribute for the blocking implementation, in order to implement some kind of synchronization mechanism for the async version.

3. Should I add the Dm: crate::DriverMode generic and only provide the Blocking implementation for the xtensa version of the Adc driver (and the esp32 Driver too) or leave it as is without the extra parameter? Done

[MabezDev]

So sorry for the delay in review here, we cut a release in between this PR meaning most of resources were dedicated to that, I hope you understand :).

I have a few initial comments, mostly because I'm not that familiar with ADC in general.

[davoclavo]

Thanks for the feedback, and totally understandable that things were busy during the release :)

Unrelated question: I have been trying to tackle pending issues marked with "help wanted" in gh to learn and contribute, but is there any other higher priority work that could be tackled via contributions or is that the right approach?

[MabezDev]

Unrelated question: I have been trying to tackle pending issues marked with "help wanted" in gh to learn and contribute, but is there any other higher priority work that could be tackled via contributions or is that the right approach?

Thanks for the interest! We're definitely keen on any helping hands, and your contributions so far have been stellar! We haven't really been using the help wanted label that much, but I can try and go through our backlog in the next few days and label some good issues for community contributions.

In general though, we're happy to take any contributions - this is an early stage project, and the teams current focus is a stable release. If there is anything that interests you in the issue tracker, then please feel free to work on it, you're welcome to ask to be assigned to certain issues too. We're more than happy to help and review PRs (in a more timely fashion from now on, I promise :D).

[MabezDev]

LGTM! Thanks for this!

I have a small nitpick about that todo comment, if you don't mind addressing that

[bugadani]

Thank you!