Add burst transfer support to DMA buffers

[Dominaezzz]

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

Adds a is_burstable to Preparation, allowing DMA buffer implementations to declare whether they conform to the alignment required for burst transfers.

Testing

HIL tests

[bugadani]

Is a reason to manually disable burst mode? If a particular transfer is "burstable", shouldn't we try to enable burst mode automatically? Right now we keep it disabled by default, and waste 2 bools per DMA channel to track whether burst mode is enabled, and I'm wondering if this is necessary at all.

[Dominaezzz]

The only reason I can think of is bandwidth. I unfortunately don't know enough about the hardware to say if there's no consequences for having 8 burst transfers going at the same time.

Though if there are no consequences then why do DMA channels have priorities. I just chose not to assume.