Adding back crank tool

[kshyju]

Adding back crank tool.

This PR consists of two commits. The first commit restores the original changes that were removed in PR #9992. The second commit introduces additional updates made while validating the tool usage flow. So far, validation has been completed for the Windows OS use case. I will address validation for Linux OS (and cleanup after) in a separate PR. A wiki page detailing the usage instructions is currently being drafted in the engineering wiki (WIP) and will be shared with the group later.

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

[jviau]

Is this the only way to include crank agent? Or can we use https://github.com/dotnet/crank and have a step to install that tool in CI?

[kshyju]

Is this the only way to include crank agent? Or can we use https://github.com/dotnet/crank and have a step to install that tool in CI?

The change in this PR is to support local developer experience such as creating isolated environment on azure where the benchmarks can be executed (using crank).

[kshyju]

Is this the only way to include crank agent? Or can we use https://github.com/dotnet/crank and have a step to install that tool in CI?

The change in this PR is to support local developer experience such as creating isolated environment on azure where the benchmarks can be executed (using crank).

Synced with Jacob about this and I am trying this idea on ADO pipeline. Marking this PR as draft for now.