REP-480 Rate Limit RegEx on Query String

This is the simple version satisfying the acceptance criteria of the story.

Refer to #980 for the more complex version.
I don't think so? Since every configured parameter has to be present, we can only return early if a parameter isn't found. So the conditional is necessary.

So what if we move `matchFound` outside of the for loops and just return at the end of the method? Well, then we always check every configured parameter even if we already know that the request does not match. Additionally, the variable would default to false, but would have to be set to false for each iteration of the outer for loop and we would only set it to true if we find a match. So if the first parameter doesn't match, we should fail to match, but if the second parameter matches, the variable is set to true and we return that.

How do you envision this logic?