Activity log metadata enrichment

[nelsonkopliku]

Description

This PR introduces a MetadataEnricher enriching metadata extracted from activity parsing.

Depends on #2992, see also #2951

The rationale behind is improving human-friendly identification of the resource the activity log entry is related to and improving log searchability.

The thing could be summarized as: adding a human friendly resource name to the activity log metadata when it does not already have one

• host -> hostname - field named hostname
• cluster -> cluster name - field named name
• database -> sid - field named sid
• sap system -> sid - field named sid
• application instance -> instance number (always present when needed, no enrichment required)
• database instance -> instance number (always present when needed, no enrichment required)

I just kept field names as they come from the read model (that is why we have hostname for a host and name for a cluster).
Had thought of options where:

• we always enrich with component_name|resource_name|name or the like
• making name for clusters clustername to be consistent with hostname

Open for feedback.

How was this tested?

Automated tests.

[dpulls]

🎉 All dependencies have been resolved !