[Bug]: generic parameters are not used for route creation

[TimothyMakkison]

Describe the bug 🐞

Refit will search through an objects properties and add them as queries, even if the the parameter is generic. I notied that it doesn't do this for generic parameters, I don't know if this is an oversight or a deliberate choice.

Step to reproduce

[Get("/foos/{request.someProperty}/bar/{request.someProperty2}")]
Task GetFooBars(PathBoundObject request);

// http://foo/foos/1/bar/barNone
fixture.GetFooBars(new PathBoundObject() { SomeProperty = 1, SomeProperty2 = "barNone" });

// generic version
[Get("/foos/{request.someProperty}/bar/{request.someProperty2}")]
Task GetFooBars<T>(T request);

// error trying to find a matching route parameter
fixture.GetFooBars(new PathBoundObject() { SomeProperty = 1, SomeProperty2 = "barNone" });

Reproduction repository

https://github.com/reactiveui/refit

Expected behavior

Matching properties in the generic object to would be used to create the route. I'm not sure if people would have a use case for this.