Use swiftwasm/setup-swiftwasm instead of swiftenv on CI

[github-actions[bot]]

Time Change: +293ms (1%)

Total Time: 18,326ms

Test name	Duration	Change
Serialization/JavaScript function call through Wasm import with int	24ms	-1ms (5%)	✅

View Unchanged

| Test name | Duration | Change | | :--- | :---: | :---: | | Serialization/JavaScript function call through Wasm import | 22ms | +1ms | | Serialization/JavaScript function call from Swift | 194ms | +5ms (2%) | | Serialization/Swift Int to JavaScript with assignment | 440ms | -7ms (1%) | | Serialization/Swift Int to JavaScript with call | 1,385ms | +9ms (0%) | | Serialization/JavaScript Number to Swift Int | 464ms | -4ms (0%) | | Serialization/Swift String to JavaScript with assignment | 505ms | -5ms (0%) | | Serialization/Swift String to JavaScript with call | 1,487ms | +19ms (1%) | | Serialization/JavaScript String to Swift String | 5,853ms | +132ms (2%) | | Object heap/Increment and decrement RC | 7,936ms | +151ms (1%) |

View Baselines

| Test name | Duration | | :--- | :---: | | Serialization/Call JavaScript function directly | 3ms | | Serialization/Assign JavaScript number directly | 3ms | | Serialization/Call with JavaScript number directly | 3ms | | Serialization/Write JavaScript string directly | 3ms | | Serialization/Call with JavaScript string directly | 3ms |

[kateinoigakukun]

The old main branch expects to have swiftenv, so perf job is failing now. But it will be back to green after merging this.