Micronaut should suggest micronaut-http-validation if http-related annotations are used

### Description

If a project uses annotations like `io.micronaut.http.annotation.Get` and does not include `io.micronaut:micronaut-http-validation` annotation processor dependency, the following code can still compile:

```
@Get("/{idx}")
public Optional show(Long id) {
return genreService.findById(id);
}
```
the error will be discovered at runtime:

```
{"message":"Bad Request","_links":{"self":{"href":"/genres/1","templated":false}},"_embedded":{"errors":[{"message":"Required argument [Long id] not specified","path":"/id"}]}}
```

NBLS should detect the situation and suggest the dependency is added to the project.

### Use case/motivation

Better user assistance with Micronaut project development

### Related issues

_No response_

### Are you willing to submit a pull request?

Yes

No source file or test is named. Start by locating the NBLS logic that inspects Micronaut annotations and proposes project dependencies; done means a project using the cited HTTP annotations without micronaut-http-validation receives a dependency suggestion.

Written by the indexing model from the issue text.