Add container name and reuse logic for rvc-intel-dev

[axion9]

Description

This PR updates the docker_run_rvc_img.sh script to improve usability and reproducibility when working with the RVC Intel development environment. The current script does not provide a name, thus it uses an auto-generated name. This causes additional executions of the script to generate n number of containers. The fix provides a container name (rvc-intel-dev) and checks for its existence prior to creating a new container. Both branches of logic dump the user into an interactive bash shell as was previously seen

Any Newly Introduced Dependencies

No

How Has This Been Tested?

This has been tested by running the script with the rvc-intel-dev container already existing to test the "start the existing container " logic, as well as with that container removed to test the "create a new named container" logic.

Checklist:

• I agree to use the APACHE-2.0 license for my code changes.
• I have not introduced any 3rd party components incompatible with APACHE-2.0.
• I have not included any company confidential information, trade secret, password or security token.
• I have performed a self-review of my code.