[JENKINS-45989] Git client support multiple patterns in getRemoteReferences

So that git-plugin discoverBranches can discover non standard branches i.e. branches not in refs/heads/* but other paths (as provided) by ref specs, the git-client plugin needs to be able to accept "pattern" for gitRemoteReferences because current functionality will only accept a single pattern and an attempt to put multiple patterns in the current implementation causes the "pattern" argument to concatenate the patterns as single string which doesn't appear to match anything

---
Originally reported by jolykins, imported from: Git client support multiple patterns in getRemoteReferences

• status: Open
  
• priority: Minor
  
• component(s): git-client-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251211-071809
  

Raw content of original issue

So that git-plugin discoverBranches can discover non standard branches i.e. branches not in refs/heads/* but other paths (as provided) by ref specs, the git-client plugin needs to be able to accept "pattern" for gitRemoteReferences because current functionality will only accept a single pattern and an attempt to put multiple patterns in the current implementation causes the "pattern" argument to concatenate the patterns as single string which doesn't appear to match anything

environment

```
Windows 32, 64 - All supported versions

Git-Client plugin version 2.5.0

Jenkins minimum version 1.625.3
```