Issue Summary

UpgradeTask100004AddAllowlistRecords fails to parse Git SSH URLs in SCP-like syntax (user@host:path format), causing repositories to be skipped during allowlist initialisation.

Steps to Reproduce

• Configure Git repositories in Bamboo using SCP-like SSH URL format  (e.g., git@example.com:team/project1.git) 
• Upgrade Bamboo to version 11.0.5 or later
• Monitor the upgrade logs during the UpgradeTask100004AddAllowlistRecords execution
• Observe parsing failure messages in the logs for SCP-like SSH URLs

Actual Results

2025-09-25 07:42:28,550 INFO [24-UpgradeTaskBackgroundThread:pool-25-thread-1] [UpgradeTask100004AddAllowlistRecords] Can't parse URL git@example.com:team/project1.git, error: Illegal character in scheme name at index 3: git@example.com:team/project1.git
2025-09-25 07:42:28,550 INFO [24-UpgradeTaskBackgroundThread:pool-25-thread-1] [UpgradeTask100004AddAllowlistRecords] Can't parse URL git@example.com:team/project2.git, error: Illegal character in scheme name at index 3: git@example.com:team/project2.git
2025-09-25 07:42:28,558 INFO [24-UpgradeTaskBackgroundThread:pool-25-thread-1] [UpgradeTask100004AddAllowlistRecords] Can't parse URL git@example.com:user/repository.git, error: Illegal character in scheme name at index 3: git@example.com:user/repository.git

Expected Results

Base URLs should be extracted and added to the allowlist. The upgrade task should extract the host portion (e.g., ssh://example.com) and add it to the allowlist automatically.

Workaround

Manually add a regular expression pattern to the Allowlist to cover the affected Git repositories:

• Navigate to Administration → Security → Allowlist
• Add a new allowlist entry with the following settings:
• Type: Regular Expression
• Expression: ssh://example.com:.* (replace example.com with your actual Git server hostname)