Use pattern matching in refFilterForPush

One popular branching strategy, when dealing with maintenance/patch releases, is to late-cut branches. That is, you end up with something like:
```
- main
- releases/v1
- releases/v1.4
- releases/v2
- etc
```
There may or may not be a floating major/minor release branch, depending on whether there are any bug fixes for any particular released version.

The problem is that currently `refFilterForPush` would require listing all such branches explicitly, meaning modifications to CI scripts for each release.

Instead, it would be nice if `refFilterForPush` supported pattern matching/globbing:
```yaml
- name: Pre-build dev container image
uses: devcontainers/ci@v0.3
timeout-minutes: 10
with:
imageName: someRepo/someImage
imageTag: sometag
subFolder: src
push: filter
refFilterForPush: |
refs/heads/main
refs/heads/releases/v*

```

Commencez par le point d’entrée refFilterForPush et l’exemple YAML de l’issue. Confirmez comment les refs exactes sont actuellement sélectionnées, puis définissez et vérifiez la correspondance pour refs/heads/main et refs/heads/releases/v* afin que les branches de release n’aient pas besoin d’être listées individuellement.

Rédigé par le modèle d'indexation à partir du texte de l'issue.