Log an event for Alert generation

### Current Behavior:
In Dependency-Track 4.3.4, alert failures (eg, slack rate limit exceeded) are logged as ERROR. However, there is no INFO level logging for the generation of alerts.

### Proposed Behavior:
Alert generation should be logged as INFO events, identifying the alert name and the project which generated it.

Use cases:
* Configure a new alert and validate in the log that it was generated. Last week, I implemented DT to DT BOM replication using Benthos as an intermediary and things were not initially working. Without alert logging in DT it was harder to trouble-shoot the problem.
* Receive a "New Vulnerability Identified" alert and have no idea at which which project generated it. The log would identify the project (ideally, the alert itself should include the info.. but a log event would be a quick-fix).
* Observe in the logs that there is **no** alert associated with a particular project. This might indicate incorrect configuration of "Limit to".