drivers: can: transceivers are initialized after controllers #45219
Description
Describe the bug
The default initialization priority for the CAN transceiver drivers is set to 70. The CAN controllers have a default initialization priority of 50, but CAN controller drivers depend on the CAN transceivers.
Expected behavior
CAN transceiver drivers should be initialized prior to CAN controller drivers by default.
Impact
Users of the CAN transceiver drivers have to manually change their initialization priority.
Environment (please complete the following information):
- OS: Ubuntu Linux 20.04 LTS
- Toolchain: Zephyr SDK v0.14.1
- Commit SHA: 04836af
Additional context
Originally noticed in #45216