Add Peak CAN driver

[Notgnoshi]

I don't have a way of testing this, so I have no idea how far off it is.

[JannesBrands]

I completed the implementation of PCAN that supports all interfaces. Anyway I dont have any PCAN to test it.
https://github.com/JannesBrands/AgIsoStack-rs/commit/273dfd6f51b87dbeb63aad20beb0ea5340a03e04

[Notgnoshi]

Fedora PCAN-Basic installation instructions

sudo dnf install kernel-devel popt-devel
tar -xzvf peak-linux-driver-8.16.0.tar.gz
cd peak-linux-driver-8.16.0/
make KERNEL_LOCATION=/usr/src/kernels/6.5.9-200.fc38.x86_64/ clean
EXTRA_CFLAGS=-Wno-error=incompatible-pointer-types make KERNEL_LOCATION=/usr/src/kernels/6.5.9-200.fc38.x86_64/ NET=NETDEV_SUPPORT all
sudo make KERNEL_LOCATION=/usr/src/kernels/6.5.9-200.fc38.x86_64/ install

Question: Should this be a netdev or chardev network device? The peak driver documentation says they now default to using chardev.

forward example application instructions

Build the forward example like so

cargo run --example forward --features tracing,socketcan,peak --input-driver socketcan --input-interface can0 --output-driver pcan --output-interface USB0

This will read from the can0 socketcan interface (which you can use cansend can0 123#44556677 to send fake data on) and write to the USB0 pcan interface. I think it's maybe possible to create a virtual pcan device?

I don't know enough about PCAN to know if that would be easy to read from to test, so I think I'd use forward to read from USB0 and forward to can1 and use candump can1 to read back to the console for verification.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
src/driver/driver.rs	0.00% <ø> (ø)
src/network_management/control_function.rs	15.78% <ø> (ø)

... and 2 files with indirect coverage changes

📢 Thoughts on this report? Let us know!