Tracking issue - improve FSI debugging #17306

FSharp Interactive debugging was never good, and it has got much worse.

This is a tracking bug to try to collect the activities that may improve it.

• Debugging can't find source. The generated multi-emit symbol files do not contain source.
• Performance: Symbol files are always generated even when not debugging
• Watch variables do not work: multi-emit fsi debug -- watch variables don't work #14572
• Local variables do not work: related to multi-emit fsi debug -- watch variables don't work #14572
• There should be a separate set of configurable options when debugging, such optimization off, tailcall off.
• Debugging should not require disable "Just my code": Cannot debug FSI with VS 2022, unless adjusting "Enable Just My Code" setting, and not wanting to use other debugger features #17148,
• While using the VisualFSharp solution it should be easier to debug a local coreclr build
• Visual Studio selects the highest version of the sdk installed on the machine when executing scripts in FSI Visual Studio selects the highest version of the sdk installed on the machine when executing scripts in FSI #17307
• We should disable the --multiemit[+/-] switch in fsi. We should disable the --multiemit[+/-] switch in fsi. #17308