Migrations to golang 1.19

[kmlebedev]

What this PR does / why we need it:

migrations to golang 1.19

[kmlebedev]

@dougbtv done. https://github.com/kmlebedev/whereabouts/actions/runs/3188703706

[maiqueb]

It's confusing to see the PR structured as is: multiple times a commit is just fixing something which was broken in a previous commit.

This makes the reviewers life harder, and renders tools like git bisect useless if this happens to be merged.

Could you please squash everything into a single commit - or structure the commits in a better way ?

Finally, I wonder if we should jump to 1.19 now. I personally would only do it once 1.18 goes EOL - meaning, I think the project's go.mod should use the oldest supported version of golang.

[coveralls]

Pull Request Test Coverage Report for Build 3188704025

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 69.659%

---

Totals
Change from base Build 3159637312:	0.0%
Covered Lines:	900
Relevant Lines:	1292

---

💛 - Coveralls

[dougbtv]

@kmlebedev any chance you can rebase? We can take another look at moving to 1.19 thanks for the PR

[github-actions]

This pull request has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.