Optionally specify branch exception patterns as regex as well as wildcard for named branch property exceptions on multibranch pipeline configuration

### What feature do you want to see added?

I am currently looking into the use of the [multibranch-params](https://plugins.jenkins.io/multibranch-params/) plugin in the property strategy configuration section of my multibranch pipeline, and I wish to set different build parameters for , using the **Named branches get different properties** option. However, I feel that the branch name pattern specifiers for property exceptions is a little limited for advanced use cases as I can only rely on specifying patterns as wildcard. For example, if I want to add a parameter (or any other available property) only to tags with a version number >= 1, I am unable to do this efficiently with wildcard logic alone. So I propose if possible, that a user can express a branch pattern as regex alongside or instead of ant style wildcard.

### Upstream changes

_No response_

### Are you interested in contributing this feature?

_No response_

Start at the multibranch pipeline property strategy configuration and the “Named branches get different properties” option described in the issue. Trace how its current Ant-style wildcard branch patterns are handled, then define support for regex patterns alongside or instead of wildcards while preserving existing behavior. Done means versioned tag patterns can select properties as requested.

Written by the indexing model from the issue text.