`cursorWordPartLeft` doesn't stop at `-` when it is excluded from `editor.wordSeparators`
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.70.1
- OS Version: Windows 11

Steps to Reproduce:

1. Change the "editor.wordSeparators" setting to exclude dash character (e.g. `{ "editor.wordSeparators": "~!@#$%^&*()=+[{]}\\|;:'\",.<>/?" }`) — this is actually a desirable setting in e.g. html/css
2. Assign a keybinding to "cursorWordPartLeft"/"cursorWordPartRight" commands
3. Observe how the definition of a "word part" differs between invocation of "editor.action.smartSelect.expand" (default kb is "shift+alt+right") and "cursorWordPart*"; "cursorWordPart*" does not behave as expected for a string `mat-button` (should have "word breaks" at the same spots as it does in `mat_button`)
`cursorWordPartLeft` doesn't stop at `-` when it is excluded from `editor.wordSeparators`
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.70.1
- OS Version: Windows 11

Steps to Reproduce:

1. Change the "editor.wordSeparators" setting to exclude dash character (e.g. `{ "editor.wordSeparators": "~!@#$%^&*()=+[{]}\\|;:'\",.<>/?" }`) — this is actually a desirable setting in e.g. html/css
2. Assign a keybinding to "cursorWordPartLeft"/"cursorWordPartRight" commands
3. Observe how the definition of a "word part" differs between invocation of "editor.action.smartSelect.expand" (default kb is "shift+alt+right") and "cursorWordPart*"; "cursorWordPart*" does not behave as expected for a string `mat-button` (should have "word breaks" at the same spots as it does in `mat_button`)