Description

Refactoring adding volumes to deletion queue
Running populateDeletionQueue() as a goroutine was causing data races with unsafe concurrent access to the http client of the powermax client while running powermax REST API queries.
Instead of running the whole function as a goroutine, only create goroutines for queue insertion operations. Since the queue insertion function needs no reference to the powermax client, there should be no issues.

Also removed a log message in locks.go that printed every 20ms.

GitHub Issues

List the GitHub issues impacted by this PR:

Checklist:

• Have you run format,vet & lint checks against your submission?
• Have you made sure that the code compiles?
• Did you run the unit & integration tests successfully?
• Have you maintained at least 85% and 90% code coverage?
• Have you commented your code, particularly in hard-to-understand areas
• Have you done corresponding changes to the documentation
• Did you run tests in a real Kubernetes cluster?
• Backward compatibility is not broken

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration