Allow glob expression in experimental_requirement_cycles

Currently `pip_parse` supports a feature to "fix" cycles among third-party packages, for example:

```
pip_parse(
...
experimental_requirement_cycles = {
"airflow": [
"apache-airflow",
"apache-airflow-providers-common-sql",
"apache-airflow-providers-sqlite",
"apache-airflow-providers-ftp",
"apache-airflow-providers-http",
"apache-airflow-providers-imap",
],
},
)
```

However it's difficult to keep this list updated, as it needs to include both direct and transitive dependencies. For example ` apache-airflow-providers-common-io` appeared in the locked requirements for one of my clients, and that broke install with a surprising error message.

It would be better to write `"airflow": ["apache-airflow-providers-*"]` so that this is robust to whatever providers are installed. https://github.com/aspect-build/rules_js/blob/main/docs/npm_translate_lock.md#list_patches is an example of a similar repo rule in JS-land which supports globs. Note that bazel-lib provides the starlark glob implementation used there.

FYI @arrdem

Start with the pip_parse implementation and its experimental_requirement_cycles handling. Compare the requested behavior with the list_patches glob support in rules_js and the bazel-lib Starlark glob implementation. Done means provider patterns such as apache-airflow-providers-* match the relevant direct and transitive requirements without requiring manual list updates.

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