Support for actions/checkout@v4 with progress and filter

[lahma]

• GH actions/checkout updated to version 4
• Added support for supplying progress
• Added support for partial checkout filters

I confirm that the pull-request:

• Follows the contribution guidelines
• Is based on my own work
• Is in compliance with my employer

[Orgl9l]

@lahma - if you're planing on completing this pull request, please can you add in the ability to specificity a path: as part of the with: to action@checkout!

My use case is to check out multiple repos side-by-side per this However to achieve this I need to check out the base/standard repo to a parallel sub-path.

Such that the block look similar to this:

      - uses: actions/checkout@v4
        with:
          path: MySpecifiedBaseRepoPath

As past of this one also need to fix-up BuildCmdPath in GitHubActionsAttribute such that Run step with invoke the launch script build.cmd from that sub folder to find the Nuke project!

White I can create an sub class of GitHubActionsAttribute and override protected GitHubActionsJob GetJobs(GitHubActionsImage image, IReadOnlyCollection<ExecutableTarget> relevantTargets) to add additional steps - in this case to make additional steps to use actions/checkout@v4's for additional repos, it seem that I can't replace the existing GitHubActionsCheckoutStep as the underlying attribute fields are private and the Property getters are also locked down.

In the ideal case, it would be great to support more of the action@checkout properties, and have built-in support to perform additional checkouts for other repos that might be needed for the build including being able to specific the additional repos SSH secret (deploy key) such that you get blocks similar to this (the assumption is that both repos will have a similar branch):

      - name: checkout additional repo Org/AbcRepo
        uses: actions/checkout@v4
        with:
          repository: Org/AbcRepo
          ref: ${{ github.ref_name }}
          fetch-depth: 0
          ssh-key: ${{ secrets.REPO_SSH_SECRET }}
          path: MySpecifiedPath

I also hope that @matkoch is supportive of this addition.

Thanks!

[leorg99]

@lahma @matkoch What is left to do so we can have this PR approved? I can help work on it. Is it just the one failing check and merge conflict?