chore: version upgrade of dependencies

[adi6859]

Description

• go: upgraded google.golang.org/grpc v1.36.1 => v1.56.3
• go: upgraded golang.org/x/crypto v0.0.0-20211117183948-ae814b36b871 => v0.14.0
• go: upgraded golang.org/x/net v0.9.0 => v0.17.0
• go: upgraded golang.org/x/sys v0.7.0 => v0.13.0
• go: upgraded golang.org/x/term v0.7.0 => v0.13.0
• go: upgraded golang.org/x/text v0.9.0 => v0.13.0

How Has This Been Tested?

• tests are performed by deploying image on vm.

Checklist:

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR requires documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have tested it for all user roles.
• I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication