Improve logging for notification publishing

[nscuro]

Description

It's hard to debug missing notifications, because Dependency-Track only logs something when an error occurred during notification publishing. Further, error logs currently do not contain any information about the notification or alert rule involved, making it harder to pinpoint where something is broken.

This PR adds more information to log messages emitted during publishing. This is done in form of PublishContext, which includes:

• The group of the notification (e.g. NEW_VULNERABILITY)
• The level of the notification (e.g. INFORMATIONAL)
• The scope of the notification (e.g. PORTFOLIO)
• The timestamp of the notification
• The subjects of the notification
  • This is limited to "affected" project(s) (UUID, name, version), component (UUID, group, name, version), and vulns (vulnId, source), as to not flood the logs
  • Aim is to provide just enough information to debug
• The name of the applicable alert rule
• The scope of the applicable alert rule
• The level of the applicable alert rule

Example log message:

Destination acknowledged reception of notification with status code 200 (PublishContext{notificationGroup=GROUP_BOM_PROCESSED, notificationLevel=LEVEL_INFORMATIONAL, notificationScope=SCOPE_PORTFOLIO, notificationTimestamp=2023-11-16T12:30:58.000Z, notificationSubjects={project=Project[uuid=8ebe0e60-0647-4f11-a048-a552ee8fe3df, name=Foo, version=123]}, ruleName=Example Rule, ruleScope=PORTFOLIO, ruleLevel=INFORMATIONAL})

This is a backport from Hyades, which already has this functionality: https://github.com/DependencyTrack/hyades/blob/v0.2.0/notification-publisher/src/main/java/org/hyades/notification/publisher/PublishContext.java

Addressed Issue

https://owasp.slack.com/archives/C6R3R32H4/p1699978082979659

TODOs

• Emit a log message when notifications have been published successfully
• Make the above configurable on a per-rule basis (required UI change)
• Implement mechanism to mask sensitive parts of destination URLs (e.g. for Slack Webhook URLs)
  • Idea discarded; Trying to mask all possible URLs is a whack-a-mole game

Additional Details

Checklist

• I have read and understand the contributing guidelines
• This PR fixes a defect, and I have provided tests to verify that the fix is effective
• This PR implements an enhancement, and I have provided tests to verify that it works as intended
• This PR introduces changes to the database model, and I have added corresponding update logic
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[rkg-mm]

Thanks, looks good from what I can see on source code level!