Incorrect argument assignment for restpath with query string or extra path info

[cognitivegears]

Description

When using restpath with a final argument against a URL that has either a query string or extra path info, this data is incorrectly included in the argument.

Steps to reproduce

As an example, take the @restpath example from the coraza documentation (https://coraza.io/docs/seclang/operators/):

SecRule REQUEST_URI "@restpath /some/random/url/{id}/{name}" \
  "deny,chain"
  SecRule ARGS_PATH:id "!@eq %{user:session_id}" "t:none"

If we try using the value of the name parameter in a subsequent rule, and then send a query string like:

/some/random/url/123/foo?q=query

Expected result

What should happen?

In this case, the value of name should be foo.

Actual result

What happened.

The value of name here is foo?q=query