[release/8.0-staging] [Test Only] Fix flaky FSW test

[github-actions]

Backport of #103873 to release/8.0-staging

/cc @jozkee @danmoseley

Customer Impact

• Customer reported
• Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Regression

• Yes
• No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

Package authoring no longer needed in .NET 9

IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.

[tarekgh]

@jozkee what is pending in the PR? and why NO_MERGE?

[jozkee]

@tarekgh it turned out to not be a straightforward port as it introduced build errors, will need to update it manually.

[PranavSenthilnathan]

Reminder that PRs into release/8.0-staging need to be completed by 4pm Redmond time on October 13 to make it into the November servicing release. After that point you'll need to target release/8.0 if you want to make the November release.

[tarekgh]

This is a test only PR anyway, I guess.