[Housekeeping] Dockerize call to "go generate" in flyteidl makefile

[eapolinario]

Describe the issue

Differences in the versions of the go toolchain cause the build scripts to fail (e.g. in flyteorg/flyteidl#321 we noticed that the build failed because we were running make generate with versions 1.18.6 and 1.19).

Instead, we should control the environment in which the calls to go generate happen, by, for example, running that in a docker container, where we can install (and test) specific versions of the go toolchain.

What if we do not do this?

We will keep seeing these little discrepancies, depending on the systems where those make targets are invoked.

Related component(s)

flyteidl

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[daniel-shuy]

I've created a PR to implement this in flyteorg/flyteidl#338, which not only dockerizes go generate, but the entire dev environment

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable.
Thank you for your contribution and understanding! 🙏