Preserve CAN port on completed TP/ETP messages

[sujandumaru]

Describe your changes

Fixes #761

Completed TP and ETP messages were created with a hard coded CAN port 0. So on port 1 or higher, destination specific multi-frame messages never reached the partner callbacks. For example a VT Get Versions response with one stored label is 9 bytes, so it goes over TP and was lost.

• TransportProtocolManager and ExtendedTransportProtocolManager now use message.get_can_port_index() for the completed message.
• Removed the tempMessage port hack and the TODO in CANNetworkManager. It stopped working after d2d47dd, and the port is now correct at the source.
• The 9 byte Commanded Address message goes over TP too, so address claiming on port 1 or higher is fixed by this as well.
• Added TransportProtocolTest.BroadcastMessageReceivingKeepsCANPort.

How has this been tested?

cmake -S . -B build -DBUILD_TESTING=ON -DCAN_DRIVER=SocketCAN
cmake --build build
./build/test/unit_tests --gtest_filter='TransportProtocolTest.*'

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud