Remove w/= and w/ operations in our repo's Q# code

[ScottCarda-MS]

Updates the Katas, Libraries, and Samples to remove w/= and w/. Copilot instruction file is also updated to instruct the copilot to avoid using these operators.

[github-actions]

Change in memory usage detected by benchmark.

Memory Report for 099fcb2

Test	This Branch	On Main	Difference
compile core + standard lib	25228490 bytes	25218942 bytes	9548 bytes

[swernli]

Of note with this one, we have a bit of a timing challenge: we should merge after the release with the feature goes out since the samples are treated as a live resource BUT we must merge before the release with the feature goes out so that the embedded samples have the new syntax. I think this means we have to hit that window of merging just before we know we are going to do an official release.

[github-actions]

Change in memory usage detected by benchmark.

Memory Report for 0f3ab13

Test	This Branch	On Main	Difference
compile core + standard lib	25228490 bytes	25218942 bytes	9548 bytes

[github-actions]

Change in memory usage detected by benchmark.

Memory Report for 78198ee

Test	This Branch	On Main	Difference
compile core + standard lib	25228490 bytes	25218942 bytes	9548 bytes

[minestarks]

This sample also shows the copy and update syntax for structs. Is this intentionally deleted?

[ScottCarda-MS]

We should probably have two new samples to replace this file: one for the copy syntax of structs and a separate one for the array index assignment.

[minestarks]

@swernli why, what do you have in mind when you say "live resource"? Do we have direct links to the main of this repo from documentation?

[swernli]

@swernli why, what do you have in mind when you say "live resource"? Do we have direct links to the main of this repo from documentation?

Yeah, last I checked we do. We still get referrals from learn.microsoft.com and quantum.microsoft.com, and I believe the learn site still deep links to the samples folder. It's possible those links have changed since I last looked though.

[billti]

We need to also consider that QCOM takes new packages and updates katas and samples regularly from them, but doesn't always update the engine/compiler when they take a new drop, so we'll need to coordinate with them to ensure we dont check in unless they'll be updating content and the compiler.