[Release/7.0][PERF]Fix Mono Dotnet Generation

[LoopedBard3]

This fixes the mono-dotnet generation for micro_mono performance runs on the release/7.0 branch as part of this: dotnet/performance#2719

A test run with this issue fixed is available here: https://dev.azure.com/dnceng/internal/_build/results?buildId=2045552&view=results

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This fixes the mono-dotnet generation for micro_mono performance runs on the release/7.0 branch as part of this: dotnet/performance#2719

A test run with this issue fixed is available here: https://dev.azure.com/dnceng/internal/_build/results?buildId=2045552&view=results

Author:	LoopedBard3
Assignees:	LoopedBard3
Labels:	area-Infrastructure-mono
Milestone:	-

[LoopedBard3]

@carlossanlop or @hoyosjs Can I get this merged if the tests come back clean? Thanks!
@hoyosjs do you happen to know if there is a good way to get the product version from the eng/Version.prop to be usable within the yaml? Adding this to main and should help keep this from being a recurring change needed down the line.

[carlossanlop]

We don't have more runway to merge this for the December release. The branch is currently closed for more changes, we will merge it when we reopen it for January release fixes.

[radical]

@LoopedBard3 Could you please explain what exactly this is fixing?

[LoopedBard3]

For mono runs, we run some extra commands to generate and combine extra necessary files for the run. This is done in perf-job.yml and the files are then used in the Microbenchmarks.proj file. Currently, the product version being used in the paths is out of date and needs to be updated, which is the goal of this PR.

[LoopedBard3]

Converted to draft to test some longer-term solutions while waiting for the ability to merge this in.

[carlossanlop]

@LoopedBard3 how is this doing? I see it's still a draft. For the January release, once the servicing branches open for merging PRs, we will only have one day to get them merged, so I want to make sure this is ready that day.

The branches open on Nov. 29th and close on Nov. 30th.

[LoopedBard3]

@carlossanlop Thanks for the heads up! At the very least, this way of fixing the problem works, but there is a different one I am testing today/tomorrow in a different branch. If the other format works, I will update this PR with that code, otherwise I will mark as ready for review and get it reviewed.

[LoopedBard3]

Running the final test: https://dev.azure.com/dnceng/internal/_build/results?buildId=2054827&view=results. The newly tested way did not work so keeping the method using sed. Found the minor error causing the other method not to work, readded it and running a test for it here: https://dev.azure.com/dnceng/internal/_build/results?buildId=2054924&view=results. If there are still issues, can revert back to old method.

[LoopedBard3]

@carlossanlop this is good to merge tomorrow with https://dev.azure.com/dnceng/internal/_build/results?buildId=2054924&view=results showing that this fix allows the broken runs to run. Thanks!

[LoopedBard3]

@carlossanlop or @hoyosjs Can I get this merged? Don't want to miss the window.

[carlossanlop]

Not ready yet. We're waiting for branding. I'll take care of it when that happens, no worries.

[carlossanlop]

Branding has been completed. Approved for 7.0.2. CI failures unrelated. Infra change only. Signed-off by area owners.
Ready to merge.