internal/router: add support for id resolving

We allow non-specific ids in API paths.
The details of the id resolution are kept
out of the router - that responsibility is
up to the API version implemention,
and will be implemented in a subsequent branch.
Is this used? Do we need to add a test for resolveUrl error?