Security fixes in GitHub actions for Unpinned Tags and Workflow yml that doesn't specifically define perms

[darrenge]

This PR contains fixes for two separate security issues found here: /~https://github.com/microsoft/garnet/security/code-scanning

1. Unpinned tag for a non-immutable Action in workflow -- Using a tag for a 3rd party Action that is not pinned to a commit can lead to executing an untrusted Action through a supply chain attack. To fix this, you tag a commit SHA to the 3rd party action call.
   For example: "uses: benchmark-action/github-action-benchmark@v1" becomes "uses: benchmark-action/github-action-benchmark@d48d326"

Each commit SHA was selected from the releases folder of each 3rd party tool. All of these were tested EXCEPT for line 74 of docker-linux.yml because that is the final build \ push step.

One of the tasks (Create PR task) in Helm needed fixed, but there was a security policy change that was preventing this task from even working, so I removed that task which also removed the initial security issue.

2. Workflow does not contain permissions -- If a GitHub Actions job or workflow has no explicit permissions set, then the repository permissions are used. Repositories created under organizations inherit the organization permissions. Often these permissions do not adhere to the principle of least privilege and can be reduced to read-only,

This is pretty simple fix where you just add this part to yml files that were missing it
permissions:
contents: read