Update go version in github actions workflows to 1.17

[Zanda256]

Current Behavior

Many of places in the workflows still mention go version 1.16 yet the adapters use go version 1.17

Desired Behavior

Workflows should also use go version 1.17

Implementation

Acceptance Tests

Mockups

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[yashtandon019]

/assign Hey @Zanda256 can you assing this to me ?

[8rxn]

Hey @leecalcote, I would like to work on this issue.

[VaibhavMalik4187]

@leecalcote Can you please assign this to me? Thanks

[leecalcote]

@VaibhavMalik4187 yes, although, we're using 1.20 now. Please use this version.

[VaibhavMalik4187]

@leecalcote The go version used in the workflows is defined as a secret variable. And I do not have access to those secrets. What should we do in this case?

[leecalcote]

I'm tagging @nebula-aac, who can offer counsel in terms of our new norm (or not) to explicitly define these versions in workflows and not in secrets any longer.

[VaibhavMalik4187]

I'm tagging @nebula-aac, who can offer counsel in terms of our new norm (or not) to explicitly define these versions in workflows and not in secrets any longer.

@nebula-aac would you like to offer your assistance in this case?

[leecalcote]

@VaibhavMalik4187 not hearing from @nebula-aac, let's proceed with displacement of the secret with an explicit version number listed. Let's jump to 1.20

[VaibhavMalik4187]

@VaibhavMalik4187 not hearing from @nebula-aac, let's proceed with displacement of the secret with an explicit version number listed. Let's jump to 1.20

On it.