[v2][Feat] Add the check-generate workflow can work in local runner for the PR from fork repo (#6845)

[SZL741023]

Tracking issue

Related to: (#6845)
Original PR: (#6952)

Why are the changes needed?

In original work flow, if files gen.Dockerfile and build-ci-image.yml have been changed, the action for build ci image will be trigger. The action for check generation will be exercise after a new ci image is built.

If the PR from fork repo, the ci image should not be rebuild and the check generate will be run in local runner.

What changes were proposed in this pull request?

build-ci-image.yml add the condition to check the PR is from the same repo or fork repo.
If PR is from fork repo, build ci image will be skip.

check-generation.yml add the condition to check the PR is from fork repo or not, and add needs: [check-generate-conatiner, check-generate-local] to call these workflows with the check fork repo condition and monitor these workflow will be failure or not.
Add two workflows files check-generate-container.yml and check-generate-local.yml file and trigger by workflow call.
One does check generate in container, the other one does check generate in local runner.
Add the extract() function in check-generate-local.yml to extract the tool versions from gen.Dockerfile to ensure that the correct version information is used.

How was this patch tested?

Ensure the PR from fork repo will not trigger the action for build ci image, and check generation will be run in locally runner.

Labels

Please add one or more of the following labels to categorize your PR:

• added: For new features.
• changed: For changes in existing functionality.
• deprecated: For soon-to-be-removed features.
• removed: For features being removed.
• fixed: For any bug fixed.
• security: In case of vulnerabilities

This is important to improve the readability of release notes.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.

Related PRs

Docs link

• main
  • Flyte 2: Cut over to Flyte 2 new backend implementation #6583
    • [v2][Feat] Add the check-generate workflow can work in local runner for the PR from fork repo ([Build] Make make gen more robust #6845) 👈

[machichima]

LGTM! Just a small nit. Also, please fix the merge conflict
Thank you!

[machichima]

I think we only need this check-generate in both check-generate-local and check-generate-container.

For others like check-go-tidy and check-mocks we can move to check-generate? So we will not see CI shows:

I would expect seeing only one Check Generated Files / check-generate-local

[SZL741023]

Both CI job check-go-tidy and check-mock also need to use the same container, so they also need to be run separately in the container and local environments.
But as per discussion, we got the new solution, if the pr from fork, build a new image to github action storage and then use it to run check-generate , check-go-tidy , check-mock
I will adjust it later.

[machichima]

LGTM! Thank you!
cc @pingsutw for final pass

[SZL741023]

Adjust the workflow, if the PR is from fork repo, it will build a local image to github storage, then do check-generate, check-go-tidy, check-mocks. Otherwise will use the image in ghcr.io.
Cause of the command container: can only pull the image from Docker Hub or ghcr.io, so in our case, it can't pull the image built locally. So use docker run to replace container: to allow the same ci job(check-generate, check-go-tidy, check-mocks) can be reused.

The base branch was changed.

[SZL741023]

New pr for this issue is #7336