Use a different set of commands to detect fourslash test updates

[jakebailey]

This is the weird set of commands I have been using locally to keep things up to date while working around the problem of "failing tests" leaving baselines behind. It seems like updatefailing should do something like this, but I think it might be too annoying.

(Sending first without the baseline update to show that it works.)

[Copilot]

Pull Request Overview

This PR updates the CI workflow to use a more comprehensive process for detecting and updating fourslash test changes. The new approach addresses an issue where failing tests leave behind baselines, which the existing updatefailing command doesn't properly handle.

• Replaces single updatefailing command with a multi-step process
• Clears failing test list, regenerates fourslash tests, and iteratively updates baselines
• Ensures all test state is properly synchronized by removing and regenerating fourslash baselines