Enable integration target version ranges

[colin-higgins]

This pull request enables specifying safe version ranges for targeted methods in integrations.

Example: An integration which is only safe to load for v6 of the Elasticsearch.Net client

[InterceptMethod(
            CallerAssembly = "Elasticsearch.Net",
            TargetAssembly = "Elasticsearch.Net",
            TargetType = "Elasticsearch.Net.IRequestPipeline",
            TargetAssemblyMinimumMajor = 6,
            TargetAssemblyMaximumMajor = 6)]

Filtering happens at ModuleLoadFinished, not the JITCompilationStarted event. Future enhancement would be to add another check within JITCompilationStarted.

[lucaspimentel]

I was thinking about how we could move this code that compares versions somewhere else and realized there's already a Version struct that we can probably use here. We can add relational operators to it (it already has an equality operator) and do comparisons like:

// compares major, minor, etc
if (target.min_version <= metadata.version &&
    metadata.version <= target.max_version) {
   // version is inside valid range
}

We could also add a method to parse from a string, and maybe even a conversion from ASSEMBLYMETADATA.

[colin-higgins]

Yeah, that's perfect. Is it okay if I visit that in the next PR? I'll be applying this to all existing integrations per the docs, as well as adding exclusion reasons as logs.

[lucaspimentel]

Sure. Thanks!