[BUG]: Incorrect default path for MAVROS configuration in Heavy and Reach Heavy configurations

[evan-palmer]

Issue Description

The bluerov2_heavy.launch.yaml and bluerov2_heavy_reach.launch.yaml files use an incorrect default path for the MAVROS configuration file. It is currently set to

$(find-pkg-share blue_description)/config/mavros.yaml

but should be

$(find-pkg-share blue_description)/config/ardusub/mavros.yaml

Steps to Reproduce

Launch Gazebo using the BlueROV2 Heavy or BlueROV2 Heavy Reach configurations

Expected Behavior

All packages should launch correctly!

Error Message

No response

Runtime Environment

This was experienced when running in the dev container. I was able to reproduce it on ROS 2 Iron, but the error should exist for the other versions as well

Additional Context

This was first raised by @SusannaMunari in #191