Replacing snforge_new with snforge_std_compatibility in tests

[cptartur]

Stack:

• Replacing snforge_new with snforge_std_compatibility in tests #3471 ⬅
• Runtime checks for _std packages #3470
• Use snforge_std or snforge_std_compatibility in snforge new #3466
• Update release workflows to publish _compatibility plugin #3465
• Add _compatibility package #3464
• Add tests for diagnostics #3424
• Fix gas tests #3421
• Disable scarb 2.10.0 specific tests #3420
• Run scarbfmt #3419
• Migrate to new macro syntax #3415

⚠️ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

[cptartur]

Not sure about this solution. It replaces snforge_std with snforge_std_compatibility in runtime. It might not cover some cases.

Alternative solution is to have scripts that replace file contents in CI and we run as always.

[cptartur]

Important, this PR causes most (or all) tests to use old plugin (v1 syntax) so it should not be treated as a test reference of macros. See PRs before this one.