Remove obsolete UUID v5 generation logic from swatch-utilizations as the Notifications service now handles message deduplication.

Since we're going to always set a new UUID when sending messages for the notifications service, we don't need the utility to build an UUID v5 identifier that was added as part of SWATCH-3794.

The notifications service implemented a deduplication logic as part of RHCLOUD-43290 (see PR). This means that the service will be using a custom dedup logic to identify events within a month period and hence we don't need to build and send an UUID v5 identified based on a concrete set of fields.

Slack thread: https://redhat-internal.slack.com/archives/C093FV0K6PM/p1763388994464759

Acceptance Criteria

• Revert the changes from SWATCH-3794