Flag incorrect use of filter (instead of action) before AlwaysReturnSniff

## What problem would the enhancement address for VIP?

Code that uses a filter instead of an action are being flagged with `WordPressVIPMinimum.Filters.AlwaysReturn.missingReturnStatement` when the correct developer remediation for the problematic code should be to change it to `add_action`

## Describe the solution you'd like

Flag use of `add_filter` on hooks that are most definitely only supposed to use `add_action`

Even better, use GitHub "suggestions" to show the correct change.

## What code should be reported as a violation?

`add_filter( 'rss2_item', 'attached_images' );`

## What code should *not* be reported as a violation?

`add_filter( 'the_content', 'my_filter_content' );`

## Additional context

If this raises a flag, then the `WordPressVIPMinimum.Filters.AlwaysReturn.missingReturnStatement` sniff should NOT.

Commencez par examiner le sniff WordPressVIPMinimum.Filters.AlwaysReturn.missingReturnStatement et la manière dont il traite les appels à add_filter. Comparez les exemples fournis rss2_item et the_content, puis définissez la liste des hooks et l’interaction nécessaires pour que les hooks utilisés uniquement pour des actions soient signalés, sans que la violation d’absence de valeur de retour le soit ; c’est terminé lorsque ces deux exemples produisent les résultats demandés.

Rédigé par le modèle d'indexation à partir du texte de l'issue.