Add "proxyRequest" to HttpRequestAttributes to assess performance

Proxy scenarios require calculating the exact path where a request should be sent to, considering we might have wildcard and URI param matchers in the listener path. Today that analysis is done within the app through DW but this is quite expensive in terms of processing.
We need to add the logic to the HttpRequestAttributes in a performant way to check the impact this will have in general scenarios (since in that case it will be analyzed for each app, proxy or not) and in the proxy one in particular.