feat(csharp/src/Apache.Arrow.Adbc/Tracing): allow ActivitySource tags to be set from TracingConnection

[birschick-bq]

Provides an virtual override for GetActivitySourceTags(properties) to retrieve tags when creating the ActivitySource.
Also adds the ActivitySourceName property so an ActivityListener can create a useful filter.

[birschick-bq]

@jadewang-db @jeremytang-db
Please review when you have a chance. Thanks.

[jeremytang-db]

So the idea is to be able to do something like this?
ShouldListenTo = (activitySource) => activitySource.Tags["Hosturl"] = "abc.databricks.com"
If there are mulitple instances of DatabricksConnection with the same combination of tags, wouldn't all the listeners pick up on all the activities?

[birschick-bq]

So the idea is to be able to do something like this? ShouldListenTo = (activitySource) => activitySource.Tags["Hosturl"] = "abc.databricks.com" If there are mulitple instances of DatabricksConnection with the same combination of tags, wouldn't all the listeners pick up on all the activities?

@jeremytang-db

One option is to start a new Listeners for each connection - in which case, you would just use a new Guid for each connection/listener combo.

Or, more complicated is that you hash the connection/token to produce a unique reproduceable value that represents the Id and only start a new Listener when that Id doesn't already exist. But this will be more complicated in the Dispose() code to ensure the last source won't send any more messages.

this.SourceId = CalculateSourceId(properties);
...
ShouldListenTo = (activitySource) => 
    activitySource.Tags.Any(t => t.Key == "DatabricksSourceId" && t.Value?.Equals(this.SourceId) == true)

[jeremytang-db]

@birschick-bq
So if I understand correctly, for the first approach:

1. Each connection generates a GUID
2. Add the GUID to the ActivitySource tags
3. Each connection creates a Listener and passes their own GUID to it
4. Each listener checks for the GUID in the activitySource tags to listen to

[birschick-bq]

@birschick-bq So if I understand correctly, for the first approach:

1. Each connection generates a GUID
2. Add the GUID to the ActivitySource tags
3. Each connection creates a Listener and passes their own GUID to it
4. Each listener checks for the GUID in the activitySource tags to listen to

That is correct. This filters out any messages not generated by your connection. And ShouldListenTo is not called for every Activity, but two times for each ActivitySource (==TracingConnection).

The ActivityListener can be instantiated inside the Connection and be disposed when the connection disposes.

[CurtHagenlocher]

This is a binary breaking change. Was this class already part of the last release? If we had "declared 1.0" and already included this class in a public release then we'd want to add an overload instead of changing the signature. (As we are not yet at 1.0, I think it's probably okay not to worry about binary compatibility in this case.)