RMT fix filter threshold max value

[enelson1001]

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

Please provide a clear and concise description of your changes, including the motivation behind these changes. The context is crucial for the reviewers.

Testing

Describe how you tested your changes.

[enelson1001]

Well shoot that was disappointing.

1. Change log - Which section do I add - RMT: Fix filter threshold , remove check (RMT fix filter threshold max value #3192)
2. I see now that I just need to remove the check on the value of the filter threshold. But not sure why this didn't get picked up when I ran cargo build -- release and cargo clippy?

[Dominaezzz]

1. Change log - Which section do I add - RMT: Fix filter threshold

Either Changed or Fixed.
The reason I'm not insisting on Fixed is because you could argue this wasn't a bug, it was just a limitation.

[enelson1001]

I think something must be wrong with esp32h2 tests?

[Dominaezzz]

LGTM. I've spot checked the TRMs of the S2,S3,C6 and H2. (The rest are probably the same)

Fixes #3183

[enelson1001]

I have printed out the RMT section of the TRM for ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2 but couldn't find TRM for ESP32-C2. So I did check these implementations. But thank you for also looking.

[MabezDev]

Thanks for the PR!