…tionality

- Implemented tests to resolve names to expected formats, including handling of various repository URLs.
- Added tests to ensure exceptions are thrown for invalid project names.
- Created tests for hub provider creation based on provider names.
- Developed tests for parsing Git URLs and extracting relevant information.
- Included tests for resolving script names from manifests and filtering remote branches.
- Enhanced Git config parsing tests to validate remote URLs and domains.

These additions improve test coverage and ensure the robustness of the AssetManager class.

Signed-off-by: Edmund Miller <[email protected]>

Signed-off-by: Edmund Miller <[email protected]>

…thod

Modify git repository initialization in test to use Git.init() with explicit master branch setting

Signed-off-by: Edmund Miller <[email protected]>

…it config scenarios

Expand test coverage for Git configuration parsing by adding scenarios for:
- Multiple remote URLs
- Non-default branch configurations
- Custom default branch names

Signed-off-by: Edmund Miller <[email protected]>

…module configuration

Expand AssetManagerTest with new scenarios:
- Handling gitmodules configuration with list and string inputs
- Testing manifest file parsing with malformed and missing configurations
- Adding submodule operations test
- Verifying repository error handling

Signed-off-by: Edmund Miller <[email protected]>

Signed-off-by: Edmund Miller <[email protected]>

…ility and structure

- Consolidate assertions using 'with' for better clarity.
- Update test names for consistency and clarity.
- Enhance gitmodules configuration tests to handle both array and string formats.

Signed-off-by: Edmund Miller <[email protected]>

- Updated `getScriptFile` method to use a fallback for revision info when git revision cannot be retrieved.
- Added `getDefaultRevision` method to return the appropriate default revision, accommodating tags and commit hashes.
- Enhanced tests in `AssetManagerTest` to validate default branch and revision behavior, ensuring consistency across various configurations.

- Introduced `@Tag("revision")` to multiple test cases to categorize them for revision handling.
- Added a new test case to validate the use of `defaultRevision` in checkout logic, ensuring it correctly retrieves the specified version from the manifest.

This enhances the clarity and organization of tests related to revision management in the AssetManager.

nextflow-io#5610 (comment)

This change allows the AssetManager to properly use Git's default branch when no explicit branch is specified in the manifest. Now the chain of fallbacks will be:

1. Use manifest's defaultBranch if specified
2. Use Git's remote HEAD reference via getRemoteBranch()
3. Use DEFAULT_BRANCH ('master') as the final fallback

This provides more flexibility by respecting the repository's actual default branch configuration rather than assuming 'master'.