URL dispatch depends on route registration order rather than convention

## Expected Behavior

URL dispatch works in the same way regardless of configuration order.

## Current Behavior

If a handler with Path extractor is registered before the nested endpoint it will throw an error like this:
`cannot parse "ROUTE_URL" to a i64 `

## Your Environment

- Rust Version (I.e, output of `rustc -V`):
`rustc 1.62.1 (e092d0b6b 2022-07-16)`
- Actix Web Version: `4.2.1`