Maintenance and support for Go major versions

[nodivbyzero]

This continues the discussion from #1339 regarding the maintenance and support of major versions.

[nodivbyzero]

Here are a couple of suggestions:

1. Align the Go version with the one used in gin-gonic/gin, as specified in their go.mod file.
2. Include a section similar to the AWS SDK for Go V2 README https://github.com/aws/aws-sdk-go-v2/blob/2c8f69732f75e2400d41a5599ee8b50a78ba1ff0/README.md?plain=1#L18-L33.

[deankarn]

Been reading a lot about it, will find some time to type it all out this weekend but thinking language version shouldn't be considered a breaking change.

I realize that's spicy comment but when I get around to posting the reasoning I think it will make a little more sense; this is one of those there are pros and conns on both sides of it.

[zemzale]

I don't feel it's that spicy at all, since for the most part, when required most libraries jump to newer versions of golang without thinking twice about it.

I don't think we have to align with gin, but aligning with go release policies of supporting the two latest versions should be what we aim for.