Restore how the dask worker node group is selected by default

[iameskild]

Reference Issues or PRs

What does this implement/fix?

• I thought I tested this PR but it appears I didn't. That PR does fix another bug but accidentally breaks how the dask worker node group selection works by default.

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[aktech]

It's quite surprising that Kubernetes tests and Provider Tests are skipped. 🤔

[viniciusdc]

It's quite surprising that Kubernetes tests and Provider Tests are skipped. thinking

Could it be this line?

if: github.event.pull_request.head.repo.name == github.repository || github.event_name != 'pull_request'

Maybe with a push to this branch, the action will be triggered... this is another good example on why we need to refactor the CI/CD, at least the triggering logic

[aktech]

We can add this job in the PR at the start to find out:

  precheck:
    name: "Check for following jobs"
    runs-on: ubuntu-latest
    steps:
      - name: Check
        run: |
          echo "HEAD Repository: ${{ github.event.pull_request.head.repo.name }}"
          echo "github.repository: ${{ github.repository}}"
          echo "github.event_name: ${{ github.event_name }}"
          echo "Should the following job run:"
          echo ${{ github.event.pull_request.head.repo.name == github.repository || github.event_name != 'pull_request' }}

[viniciusdc]

LGTM

[iameskild]

Thanks @viniciusdc @aktech! Did you want to test that section in this PR?

[aktech]

We can but I don't want to block this PR, since it's approved, let's get this one in, we can test in a separate PR.