New tabs don't launch in the directory of the first tab when launching WT via cmd.exe shorthand

### Windows Terminal version

1.15.3466.0

### Windows build number

10.0.22621.1105

### Other Software

_No response_

### Steps to reproduce

Reproduce actual (broken) behaviour:
1. When in a particular folder with Explorer, open Terminal by typing "cmd" in the address bar
2. Create a new tab in the opened Terminal window

Reproduce expected behaviour:
1. When in a particular folder with Explorer, open Terminal by typing "wt" in the address bar
2. Create a new tab in the opened Terminal window

### Expected Behavior

The new tab should have the same working director as the first tab, if settings.json is correctly setup.
This is already the case when launching Terminal through the "wt" shorthand, but not via "cmd".

### Actual Behavior

The new tab always starts in "C:\Windows\System32" regardless of the starting directory of the first tab.
When launching Terminal through the "wt" shorthand, the new tab will start in the correct directory.

Reproduce the behavior by launching Windows Terminal with the cmd.exe shorthand from an Explorer directory, then compare it with the wt shorthand. Trace the startup paths for cmd and wt and verify that creating a new tab preserves the first tab's working directory instead of using C:\Windows\System32.

Written by the indexing model from the issue text.