Use `embedded_can` traits & types

[wojciech-graj]

The embedded-can crate seems to be the de-facto standard CAN interface in rust, being used by e.g. embassy and the socketcan crate. As such, I believe it would make sense to use it in this crate.

At a bare minimum, this would require implementing the Can trait on the types responsible for sending/receiving CAN frames, and implementing embedded_can Frame on Frame.

However, a more full transition could be achieved by completely replacing the automotive Identifier with that from embedded-can, and removing the send/recv methods on the sender/receiver types. I think this would be the best approach.

@pd0wm please let me know what your thoughts are, as I'd be happy to implement these changes.

[pd0wm]

Last time I looked there was no support for async Can traits, and no CAN-FD support for Frame. There are open issues/PRs for these features, so think we'll need to wait for those to be merged if we want to add support.

• CAN FD support  rust-embedded/embedded-hal#578
• Add async API for CAN rust-embedded/embedded-hal#585

I'm open to replacing the Identifier type, I think it's very similar anyway. For the Frames types I'd like to implement proper types where only legal states can be represented (e.g. an RTRFrame does not contain any data, only FDFrames have a BRS flag, etc), see #60. We can then implement the embedded-can traits on these custom frame types.