use correct volume in carma script

[MishkaMN]

PR Details

Description

Issue is described in the jira link. But basically when carma config install is called, it created temporary volume of carma-config-tmp to read the .env file.

However, currently it is mistakingly reading it from carma-config volume, instead of carma-config-tmp, which doesnt exist yet (or if existed, it would end up downloading previously set carma-config and not the one specified in install command). This PR fixes it with correct volume.

It was not caught before because I kept resetting or installing same images to verify. If different image was tested, I had tested 4.5.0 which doesnt use .env file.

Related GitHub Issue

NA

Related Jira Key

https://usdot-carma.atlassian.net/browse/ARC-141

Motivation and Context

Fix for bug introduced in #2409

How Has This Been Tested?

black pacifica and fusion vehicles

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.

[sonarcloud]

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