Searching for alarms in the v2 API with a reductionKey that includes a comma or semicolon results in a 500 error

While attempting to move an integration that uses the v1 alarms REST API to v2 due to poor performance in v1 (NMS-12764), we found that attempting to filtering on reductionKey fails if the query includes a percent-encoded comma or semicolon, despite the fact that search.decode.values is set to true in the CXF-RS config.]

Stack trace attached.