Terminals with history restored when reopening windows doesn't source interactive shell profiles (such as .zshrc)

Is there an existing issue for this bug?

• I have searched the existing open issues and found none that apply.
• If I find any issue of interest that is related or closed, I will included a link to it in this issue.

Required Troubleshooting Steps

• I have read and performed the troubleshooting steps
• I have tried both values of the remote.SSH.useLocalServer setting
• My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
• I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar

[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log

[PASTE LOG HERE WITHIN THE BACKTICKS TO FORMAT]

Expected Behavior

Terminals with history restored should behave exactly like newly created ones where Interactive shell profiles (such as .zshrc) are sourced, so that all the settings inside it are correctly set.

Actual Behavior

Currently terminals with history restored doesn't source my user's .zshrc profile, thus making things like shell prompts different than newly created terminals.

Steps To Reproduce

1. create a terminal in an opened ssh connection's folder
2. input any amount of commands in the terminal
3. close the folder
4. reopen the folder

Anything else?

No response

The issue does not name a source file or test. Reproduce the terminal restoration steps in a Remote-SSH window and compare restored and newly created terminals, then use the Remote-SSH troubleshooting steps and logs to identify where interactive shell profile sourcing differs; done means restored terminals source the profile and match newly created ones.