modules test on a private modules server requires --git-remote

Description of the bug

I have setup a private version of the modules repository, with the files in the same sort of structure.
When trying to develop on a clone of that repo, I find that nf-core modules create modulename works fine, but nf-core modules test modulename gives an error:
Cannot find directory 'modules/nf-core/modulename'. Should be TOOL/SUBTOOL or TOOL

Adding --git-remote to point at the URL for the repo that I have currently checked out, does indeed work.

I also had issues with nf-core modules lint modulename initially without adding the --git-remote option, but it is currently working for me without adding the --git-remote.

@awgymer on slack said:

Ok it’s this line. Rather than use the org_path it’s choosing to use the self.modules_repo.repo_path value which, I am pretty sure, is just the org_path but for the remote. And since you haven’t explicitly set the remote is defaulted to nf-core.

Command used and terminal output

nf-core modules test modulename
`Cannot find directory 'modules/nf-core/modulename'. Should be TOOL/SUBTOOL or TOOL `

System information

nf-core 2.14.2.dev0
nextflow 24.04.2.5914

Start with the modules test handling in nf_core/components/components_test.py at lines 126-127, then reproduce nf-core modules test modulename against a private modules repository without --git-remote. Compare the repository path used by modules create and modules lint; done means testing the checked-out private repository works without explicitly passing its remote, with regression coverage for that command.