fix: pin go version Dockerfiles

[alexanderbez]

Description

closes: #11709
ref: #11663

Pin against Go versions in Dockerfiles

cc @faddat

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[julienrbrt]

lgtm

[faddat]

#11688

@alexanderbez FYI, if we definable don't want versions to "roll" then we probably shouldn't use Arch-- that's kind of its precept.

[alexanderbez]

@faddat I'm open to your suggestions. I just think it's

1. Best to pin against explicit dependency versions
2. This PR actually fixed the localnet stuff