Correlate Database audit log entries with the asset id of the data link used for the connection, if available

[radeusgd]

If a database connection was opened through a data link, it is audited. If the data link was from the Enso Cloud, we want to add its assetId to the metadata of each log entry.

For data links that are not in the Cloud (local file system etc.) we cannot have a stable identifier like the assetId, so we don't add anything similar.

• The data link instance fetched from the Cloud needs to be aware of its asset id - modify the data link read logic to be able to supply optional id.
• That ID needs to be passed to the CloudAuditedConnection, probably through additional JDBC properties.
• Tests need to be written
  • The challenge is: our Cloud mock does not support reading files/datalinks, but we wanted to rely on the mock for testing the logs. Some solution needs to be picked:
    1. Add basic datalink support to the mock, and run the tests on there.
    2. Run the tests on the real cloud deployment (in local testing the stability seemed okayish - but hard to tell how it will be on CI).
       • the benefit is we get a real integration test, as the mock and cloud can diverge,
       • we still need to implement Creating datalinks in Enso Cloud programmatically #9673 first, to be able to prepare the data link used in the test.