Enable Wildcard Pattern Matching in tag_blocklist and tag_exclusions

Problem/Motivation

As an administrator I need to define dynamic tag exclusion patterns in the govcms_akamai_purge.settings.yml configuration so that tags generated at runtime (for example my_plugin:[random-hash]) can be excluded without specifying each value manually.

Steps to reproduce

The current configuration entries tag_blocklist and tag_exclusions do not support wildcard patterns (for example, my_plugin:*). This limits the ability to exclude a series of dynamic or programmatically generated tags from purge requests. Admins must list every specific tag if values vary.

Proposed resolution

Noting that this will not perform wildcard purges on Akamai, which is not supported. This is for filtering before sending to Akamai only.

1. The configuration accepts wildcard patterns (*, ?, or similar) for tag_blocklist and tag_exclusions.
2. The pattern matching is implemented in the module’s tag filtering logic before generating the purge request.
3. Wildcards match multiple dynamic tags (for example my_plugin:* matches my_plugin:variation1 and my_plugin:[generated-hash]).
4. The matching logic is efficient and safe (does not degrade performance).
5. Admin documentation is updated to describe wildcard usage and supported pattern syntax.

Remaining tasks

TBA

User interface changes

Support wildcard '*' in the config (similar to core Block visibility rules)

API changes

N/A

Data model changes

N/A