I extracted a new function (match_regex_list) from how the matching of trace_propagation_targets works right now to reuse the behavior.

One possible foot gun:
In trace_propagation_targets we do sub-string matches (as described in the documentation: https://docs.sentry.io/platforms/python/configuration/options/#trace-propagation-targets)

This could lead to unintended matches if you have two tasks task-a and task-a-b and you set exclude_beat_tasks=["task-a"] it will exclude task-a and task-a-b.

Not the best developer experience, but it is the behavior we have no in trace_propagation_targets.

Changed to always match the full task names.