Routes are registered like below:
Porpery navigation request - http://localhost:9095/Products(1)/Family
Action request - http://localhost:9095/Products(1)/ExtendSupportDate
For the above requests only the 1st route would match as they are logically the same
we might need to remove the newly added InboundAction route and just have one route for both navigation properties and actions. We would need some kind of logic in action selector to figure incoming request is for a property or function.