Multiple quick fixes offered for `@RequestMapping` into `GetMapping` etc

[BoykoAlex]

Currently OR only allows for converting @RequestMapping into precise mapping if only one Request Method is inferred from the @RequestMapping. However, if there are multiple request methods such @RequestMapping without the method parameter then it'd be useful to show a reconcile problem and offer quick fix for each method type.

Might be of some use flag all @RequestMapping annotations over methods and offer multiple quick fixes for @RequestMapping that has explicitly specified multiple request methods.

[BoykoAlex]

@martinlippert Precise annotations are GET, POST, PUT, DELETE, PATCH. This excludes OPTIONS and TRACE. Therefore if method type has OPTIONS or TRACE - no problem. Now, if there is a few request methods specified, i.e. POST and PUT. Shall I offer switching to either @PostMapping or @PutMapping?
Maybe all we want is just support @RequestMapping("/hello") kind of annotation where request method is unspecified?

[BoykoAlex]

I have pushed 78cd6ac. Just show a number of quick fixes for @RequestMapping not specifying any request methods... likely this needs to be a specific request mapping not any request method. Therefore if two or more request methods specified the annotation won't be flagged and refactoring not offerred.