deployment: try to import a given identifier as ROS package before loading an equally named regular file

This fix checks if a given identifier, which is not an absolute path, is a valid ROS package name before
trying to open a regular file with the same name as a component library (partially reverted b781fff0a9e118a658328b08eb133a881f2f1a2d).
deployment: try to import a given identifier as ROS package before loading an equally named regular file

This fix checks if a given identifier, which is not an absolute path, is a valid ROS package name before
trying to open a regular file with the same name as a component library (partially reverted b781fff0a9e118a658328b08eb133a881f2f1a2d).
Merge branch 'deployment-component-fix'
deployment: try to import a given identifier as ROS package before loading an equally named regular file

This fix checks if a given identifier, which is not an absolute path, is a valid ROS package name before
trying to open a regular file with the same name as a component library (partially reverted b781fff0a9e118a658328b08eb133a881f2f1a2d).

Signed-off-by: Johannes Meyer <meyer@fsr.tu-darmstadt.de>
Merge branch 'deployment-component-fix'