Metrics filter incorrectly handles wildcard combined with range

[Alex Bublichenko]

There is a bug in the filter implementation that is used in the aggregator rules: it incorrectly handles combination of wildcard and a range filter.

Reproduced in new unit tests: d2762b4

Example:

Create a filter "*ending.{bar,foobar}" and match it against two inputs:

some_ending.bar
some_ending.foobar

Expected result: it should match both inputs
Actual result: if fails to match the second input

[Andrew Mains]

Looks like the same issue as #1810 -- definitely a legitimate issue.

Closing as dupe.