Move interrupt related bits out of lib.rs and into the interrupt module

[MabezDev]

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.

[Dominaezzz]

LGTM

[Dominaezzz]

Suggested change

	- Removed interrupt related items from lib.rs, moved to the `interrupt` module (#2613)
	- Moved interrupt related items from lib.rs to the `interrupt` module (#2613)

[bjoernQ]

Besides the CI run this looks good to me - one thing I just discovered: Shouldn't we have an inherent set_interrupt_handler on the driver and let the trait impl just call that? (Probably should be done in its own PR - just noticed it here)

[bugadani]

Besides the CI run this looks good to me - one thing I just discovered: Shouldn't we have an inherent set_interrupt_handler on the driver and let the trait impl just call that? (Probably should be done in its own PR - just noticed it here)

Frankly speaking I don't see too much value in the trait at all.

[jessebraham]

LGTM, would also probably like to see InterruptConfigurable go away unless there is some reason to keep it, but given that it already existed can be done here or in another PR, doesn't matter to me.

[bjoernQ]

LGTM - instead of removing InterruptConfigurable we can also just make sure we have an inherent set_interrupt_handler function everywhere - but not in the scope of this PR