Add support for bourne shell (sh) shell integration

[Tyriar]

Out of all shell integration injection failures, about 42% are unsupported shell due to sh being the shell type.

[Tyriar]

Note that /bin/sh is actually bash (not symlinked) on my macOS:

[anthonykim1]

My first intuition is that we need shellIntegration.sh dedicated for bourne shell integration just like how we have ones for powershell, bash, zsh, fish.

This shellIntegration.sh file would need to mainly:

1. Send the relevant 633 escape sequences..
2. be sourced by creating temp directory(?) sh, in a way of equivalent to
   

   vscode/src/vs/platform/terminal/node/terminalEnvironment.ts

   Lines 268 to 275 in a1d87f0

   	filesToCopy.push({
   	source: path.join(appRoot, 'out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-rc.zsh'),
   	dest: path.join(zdotdir, '.zshrc')
   	});
   	filesToCopy.push({
   	source: path.join(appRoot, 'out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-profile.zsh'),
   	dest: path.join(zdotdir, '.zprofile')
   	});

[Tyriar]

@anthonykim1 I actually tried this on my break and had some problems accomplishing it, mainly because I was a little confused when testing on my mac where it was actually bash (#250316). I think in the end after analyzing the data some more, it's not worth doing this for sh. Here's the last 7 weeks in stable only:

Drilling into it on platform shows it's 0.1% on macOS and 0.7% on Linux local windows. In fact when you remove the remote-ssh extension terminals the total number drops to 1% of total terminals. Almost all of these are also remote-ssh terminals but non-extension terminals, meaning it's the user's default profile. So in those cases, it's likely #250316 would be a lot of these, and even if not I'd say it's not actually worth pursuing this since in the end it makes up much less than git bash.

Other small cases are 1.7% non-ext in containers and 16% in codespaces, both of which may be limitations of the container or #250316 as well.