[FR] Some way to have `@RequestParam(required = false)` be interpreted as `@Nullable`

I just added NullAway 0.10.10 to the build process of a collection of microservices that use Spring Boot and Feign to communicate. The interfaces that the microservices use are annotated to indicate whether the function parameters are put in the URL path , as query parameters, or as a request body. Most query parameters are optional and should be treated as nullable if they have the required = false argument to the @RequestParam annotation. Unfortunately, required = true is the default and there are many other arguments that the annotation takes.

In my case, it seems like treating the @RequestParam annotation as equivalent to @Nullable makes some sense because we use required = false 99% of the time, but I can imagine other times where the extra accuracy would be helpful.

The issue names no files, tests, or entry points. Start by identifying where NullAway interprets annotations, then establish how @RequestParam(required = false) should be represented as nullable and how that behavior will be verified.