Update GitHub actions workflows for Docker builds

[SaikrishnaBairamoni]

PR Details

Description

Related GitHub Issue

Related Jira Key

Motivation and Context

How Has This Been Tested?

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.

[MishkaMN]

I am not sure what these lines do? Is it saying to build these branches, or ignore them? carma-develop, master, release branches we do want to build right?

[MishkaMN]

I think I got my answer in private chat from Sai:
ci.yml: it will build and run units for sonar scanner analysis but does not push any images to docker hub dockerhub.yml: it will build and push of docker images when push occurs to develop, release branches, master but doesn't run any unit test or sonar scanner docker.yml: it will only build for feature branches and Pullrequest is opened, changed , merged (edited)

[MishkaMN]

Should this be carma-develp?

[SaikrishnaBairamoni]

Updated to carma-develop

[MishkaMN]

Should this be carma-develop?

[SaikrishnaBairamoni]

Updated to carma-develop