This pull request refactors how package versions are handled in benchmark configuration, moving from single-version to dual-version (Validator and SDK) support. The changes improve flexibility and clarity by explicitly specifying both ValidatorVersion and SDKVersion for each benchmark run, and updating the project file to use these properties for package references.

Benchmark configuration improvements:

• Changed PackageVersion and PackageVersionAttribute to include both ValidatorVersion and SDKVersion, allowing benchmarks to target specific combinations of validator and SDK versions. [1] [2]
• Updated the logic in CrossVersionConfigurationAttribute to use the new dual-version structure, ensuring correct version selection and job creation for benchmarks. [1] [2]

Project file changes for version flexibility:

• Refactored Benchmarks.csproj to use ValidatorVersion and SDKVersion properties for package references, enabling dynamic selection of package versions based on defined constants.

Benchmark annotation updates:

• Updated ValidatorBenchmarks to use the new PackageVersionAttribute format, specifying both validator and SDK versions for each benchmark case.