ci: Update module_name filter step

[edmundmiller]

Created a small test script to prevent re-running into edge-cases and to quickly add new test cases. If we don't hate the idea I think we can wire it up to the javascript file to avoid any copy-paste errors.

[MatthiasZepper]

I have now only tested the script in isolation, but the test cases pass for me locally as well. Thanks for the solid work!

[MatthiasZepper]

Looking at the CI failure in this PR...can it be that it was only the missing bracket in the .map() function that caused all the issues?

      - name: Get module name
        uses: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea # v7
        id: module_names
        with:
          script: |
            return [...new Set(${{ steps.filter.outputs.modules_files }}
                .map(path => path
                .replace('tests/', '')
                .replace('modules/nf-core/', '')
                .split('/')
                .slice(0, 2)
                .filter(x => !x.startsWith('main.nf') && x !== 'tests' && x !== 'meta.yml' && x !== 'environment.yml')
                .join('/'))
              )
            ];

[MatthiasZepper]

I think, that will do. Nice work!

Zizmor nags that steps.module_names.outputs.result may expand into attacker-controllable code, but I don't really see how that could be exploited, because the inputs must be a valid file path. And in the worst case, nf-core modules lint is just called with some invalid module.

[MatthiasZepper]

Not sure how this ended up in the PR, but otherwise that looks good to me.