Update go version to 1.21

[praveenkumar]

Since 1.18 is already EOL and all our tooling migrated to go-1.21

• https://endoflife.date/go

[cfergeau]

Why?

[praveenkumar]

Why?

@cfergeau added in the commit logs

[cfergeau]

I'm still not 100% sure from the commit log if this is a change which is required, or if it's something we do for consistency with the rest of our stack.
The fact that go.mod says 1.19 does not prevent us from using 1.21 or 1.22 for building.

[praveenkumar]

I'm still not 100% sure from the commit log if this is a change which is required, or if it's something we do for consistency with the rest of our stack.

The fact that go.mod says 1.19 does not prevent us from using 1.21 or 1.22 for building.

it doesn't prevent us to use latest version of golang but it also doesn't prevent some to build it on older version since it is already EOL so I am not sure what else would be best reason to have it in.

[cfergeau]

I'm still not 100% sure from the commit log if this is a change which is required, or if it's something we do for consistency with the rest of our stack.

I still have no idea about this. I think you are saying this is not a required change (required because something is broken if we try to build with go 1.19 or 1.20), but that it's better to have this for consistency/because go older than 1.21 is not supported/..., which is fine with me.

[praveenkumar]

I'm still not 100% sure from the commit log if this is a change which is required, or if it's something we do for consistency with the rest of our stack.

I still have no idea about this. I think you are saying this is not a required change (required because something is broken if we try to build with go 1.19 or 1.20), but that it's better to have this for consistency/because go older than 1.21 is not supported/..., which is fine with me.

That's what I put in the commit log, since 1.18 is outdated and our tooling already moved to 1.21