[AspNetCore 3.0] 'IRoutingFeature' cannot be extracted from context features

Describe the bug IRoutingFeature cannot be extracted from context features, leading to GetNameFromRouteContext(RouteData) not work (/user/profile/1 cannot be replaced by /user/profile/{id})

To Reproduce Steps to reproduce the behavior:

1. Create AspNet Core 3.0 project from template
2. Add Elastic.Apm.AspNetCore package reference
3. Add app.UseElasticApm(Configuration); in Startup.cs
4. You’ll see transaction name won’t be replaced by RouteData

Expected behavior Transaction name should be replaced by route data

[vhatsura]

@gregkalapos, I believe it can be closed due to #647 was merged

[yhvicey]

Looks like there’re some ways to resolve this:

1. Upgrade dependencies’ version from 2.1.0 to 2.2.0 - I’ve made a PR explorering this;
2. Use TargetFrameworks to target both netstandard2.0 and netcoreapp3.0 and have different dependencies, conditional code blocks to make this function works in AspNetCore 3.0
3. Wait for netcoreapp2.1’s deprecation - then the first action might become necessary