feat: add raise_error and log_error option to insert_hosts_to_meta filter

[bzwei]

https://issues.redhat.com/browse/AAP-17232

[mkanoor]

@bzwei should we add documentation here too https://ansible.readthedocs.io/projects/rulebook/en/latest/filters.html

[bzwei]

@bzwei should we add documentation here too https://ansible.readthedocs.io/projects/rulebook/en/latest/filters.html

Yes.

[Alex-Izquierdo]

I'm concerned about mixing scopes of the documentation. Why not create a docs/event_filter/insert_docs_to_meta.md which was the plan from the beginning and we can continue writing documentation for the rest of things?

[mkanoor]

@bzwei
With this PR changes and the issue that we had seen with the broken path

 host_path: event.payload.meta.hosts

Nothing changes, there is no log messages and there is no exception. A customer has to be told to use the new raise_exceptions option to see anything meaningful. We are back to square one. This PR doesn't help the customer self diagnose the issue. They might go back to using the limit approach.

We need to log.error by default so out of the box we see an error in the Activation log that the customer can be told to turn off by modifying the rulebook which is an easier change for them.

Maybe log_errors: True|False. True by default.

If they feel there is too much noise they could just set the log_errors: False

[Alex-Izquierdo]

Hi @bzwei Ruff is failing with:

extensions/eda/plugins/event_filter/insert_hosts_to_meta.py:52:5: PLR0913 Too many arguments to function call (6 > 5)
extensions/eda/plugins/event_filter/insert_hosts_to_meta.py:71:13: TRY400 Use `logging.exception` instead of `logging.error`

CI criteria for eda collections is a pending discussion.

In the case of PLR0913 you already have a exception but I think it must be in line #52. Anyway, since filters receives the plain args and generally speaking, I think it is perfectly reasonable to add the exception for PLR0913 in general in https://github.com/ansible/event-driven-ansible/blob/main/tox.ini#L18

In the case of TRY400 I think we want to keep the check but this case justifies a line exception.