Record branch information in modules.json

[ErikDanielsson]

Description of the bug

If a module is installed from a branch other than the default branch, commands that rely on the modules.json for version information will fail since they only look for the sha in the default branch of the repository.

Fixing this should be rather easy, just record the branch name along with the git sha in the module entry. So a new modules.jsoncould look like

{
    "name": "a/pipeline",
    "homePage": "https://a-pipeline.com",
    "repos": {
        "some/cool/repo": {
            "base_path": "modules",
            "git_url": "https://git-provider.com/some/cool/repo.git",
            "modules": {
                "first-modules": {
                    "git_sha": "<some sha>",
                    "branch": "main"
                },
                "second/module": {
                    "git_sha": "<another sha>",
                    "branch": "other-branch"
                }
            }
        }
    }
}

Command used and terminal output

$ nf-core modules -b <br> install mod
$ nf-core modules list local 
┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┓
┃ Module Name   ┃ Repository    ┃ Version SHA   ┃ Message       ┃ Date         ┃
┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━┩
│ mod           │ repo          │ sha           │ Not Available │ Not          │
│               │               │               │               │ Available    │
└───────────────┴───────────────┴───────────────┴───────────────┴──────────────┘

System information

nf-core/tools 2.5dev

[ErikDanielsson]

Closing due to merge of #1738.