feat(taskworker) Add support for glob rollout rates

[markstory]

We have 300+ tasks. That will be a lot of data to read out of options in aggregate. For smaller deployments, small namespaces, or when we have completed a namespace we could use a wildcard - * to apply the same rollout rate to all tasks. The task specific rollout rate would take precedence over the wildcard rate.

[codecov]

Codecov Report

Attention: Patch coverage is 92.59259% with 2 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
tests/sentry/tasks/test_taskworker_rollout.py	90.47%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #88853       +/-   ##
===========================================
+ Coverage   32.97%   87.73%   +54.75%     
===========================================
  Files        8512    10072     +1560     
  Lines      475426   569678    +94252     
  Branches    22372    22372               
===========================================
+ Hits       156780   499801   +343021     
+ Misses     318247    69478   -248769     
  Partials      399      399               

[evanh]

Would we also want to support wildcard suffixes? E.g.
{"test.low_rate": 0.5, "test.low_*": 0.1}

[markstory]

Would we also want to support wildcard suffixes? E.g. Would we also want to support wildcard suffixes? E.g.

Maybe? I was thinking of using this glob implementation as a catch-all for after namespaces are migrated and we want to simplify our options data.