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.

Comienza examinando el sniff WordPressVIPMinimum.Filters.AlwaysReturn.missingReturnStatement y cómo gestiona las llamadas a add_filter. Compara los ejemplos proporcionados rss2_item y the_content, y después define la lista de hooks y la interacción necesaria para que se marquen los hooks que solo se usan para acciones, pero no la infracción por falta de retorno; estará terminado cuando esos dos ejemplos produzcan los resultados solicitados.

Escrito por el modelo de indexación a partir del texto del issue.