Better support for Spring MVC annotations
The existing support for Spring MVC is a bit confusing, as the Taxi annotations and Spring annotations overlap so closely (but not exactly).
We need to balance opt-in for Spring MVC (ie., users should explicitly annotate what they want to expose to Taxi, rather than assuming that everything should have be present in the generated schema).
However, having a Spring Controller with a taxi
@Service annotation is a bit over the top.
- Omit the need for class-level annotations entirely, since these are inferrable
- Allow an optional
@TaxiServiceannotation, which may be used at the class level if it's desired to expose the service with a different name.