Fix integration test issues

[MishkaMN]

PR Details

Description

I tested the Humble SSC wrapper on Blue Lexus using the binaries I got form Hexagon.
This was basically a simple smoke/regression test that just lane follows on the innocation drive.
driver_shutdown_ros2 (hence assuming dirver_shutdown too) just needed to be built for it to successfully launch.
I will try to test on Fusion the ROS1 package if I have time.

NOTE: I tested with all develop images which are in Foxy except the ssc_wrapper.
Initially either the engage request was not being received or the ssc was just not responding (it did not shift gear etc after the engage service returned successfull).
This prompted me to use ros1_bridge and platform_ros2 as Humble, but that required minimum of 11.7 Cuda to work (by platform_ros2). This made me reinstall Nvidia and Kvaser drivers on the vehicle.

In the process, I also remembered to install libas-common on the host (it is there in the image), which is requirement for Humble SSC binary to work. I am guessing this made the trick, because now with the same setup, the Lexus was able to engage and drive using trajectory_follower control plugin.

Related GitHub Issue

NA

Related Jira Key

ARC-234

Motivation and Context

Humble Upgrade smoke test

How Has This Been Tested?

Innovation Drive Basic Lane Following

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• I have added any new packages to the sonar-scanner.properties file
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.