Update setup opt-carma script according to install guide

[MishkaMN]

PR Details

Description

During creation of CDASim comprehensive tutorial guide, I needed to include a step to setup CARMA. That writeup prompted opportunity to clean up our script that is referenced in our CARMA installation guide here: https://usdot-carma.atlassian.net/wiki/spaces/CRMPLT/pages/488472599/Setup+CARMA+Platform+Runtime

Changes include:

• No longer downloads autoware.ai just to copy its yolo contents. CARMA doesn't use camera at the moment so it is not needed. That repo is almost 400 MB+ so it is not ideal.
• Added support for setting up common static folders needed for CDASim because it is not documented anywhere, and my current write-up and existing installation guide will include them.

Related GitHub Issue

NA

Related Jira Key

https://usdot-carma.atlassian.net/browse/CXC-94

Motivation and Context

I am writing CDASim tutorial guide. And its configuration step required some changes to our installation guides, which I discovered these issues.

How Has This Been Tested?

local integration tested by calling scripts in https://github.com/usdot-fhwa-stol/carma-platform/pull/2449 and building images locally

Types of changes

• [X] 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
• [X] My change requires a change to the documentation.
• [X] I have updated the documentation accordingly.
• [X] I have read the CONTRIBUTING document. CARMA Contributing Guide
• [X] I have added tests to cover my changes.
• [X] All new and existing tests passed.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud