[path]: Possible edge-case in custom regexes that need request query

[erbesharat]

Is this a BUG REPORT or FEATURE REQUEST?:
bug

What happened:
Currently, request path and query would get merged if the record's re= field contains the "?query" word. So if a custom regex doesn't need the request query but instead is looking for the "?query" inside the request path, there probably would be an error while finding the submatches.

What you expected to happen:
Find another way to pass the request query to the custom regex without checking it via the strings.Contains() method.

How to reproduce it (as minimally and precisely as possible):
"v=txtv0;type=path;re=/?query/testing"