Update to embassy-executor 0.3.0

[bugadani]

Thank you!

Thank you for your contribution.
Please make sure that your submission includes the following:

Must

• The code compiles without errors or warnings.
• All examples work.
• cargo fmt was run.
• Your changes were added to the CHANGELOG.md in the proper section.
• You updated existing examples or added examples (if applicable).
• Added examples are checked in CI

Nice to have

• You add a description of your work to this PR.
• You added proper docs for your newly added features and code.

Updates the build-in executors to use the newest embassy-executor crate. This change means that calling a pender no longer goes through a function pointer - but it needs a runtime branch to figure out which interrupt to fire.

I renamed a macro parameter as it wasn't very well named, so that increases the noise level a bit, but hopefully will reduce future confusion potential.

This PR does not change user-facing APIs. Hopefully, I've feature-guarded the __pender function correctly, too, in case someone wants to use their own executors. Unfortunately, it is not possible to mix one of ours (thread or interrupt) with a custom executor. This tradeoff was acceptable to the embassy project, so I hope this shortfall won't cause much problems here, either.

Unfortunately, due to some transitive sadness, we have to use the git dependency until a new embassy-time is released. Thanks Jesse for the embassy-time release!

[bugadani]

My test cases, that I actually tried:

• ESP32/embassy_multicore example
• ESP32/embassy_multicore_interrupt example
• my own S3 project

All 3 test cases seem to work well so hopefully I didn't mess anything important up. I've fixed the labels of the CI jobs I copy-paste-error'ed last time.

[jessebraham]

LGTM, thanks for taking care of this!