cache script per file instead of per directory

[DanielEgbers]

Description

Currently only one script per directory is cached.

This PR adds the script file name into the cache directory path, therefore caching scripts per file instead of per directory.

Example:

Script	Current Cache	New Cache
D:\scriptA.csx	%tmp%\dotnet-script\D\execution-cache\script.dll	%tmp%\dotnet-script\D\scriptA.csx\execution-cache\script.dll
D:\scriptB.csx	%tmp%\dotnet-script\D\execution-cache\script.dll	%tmp%\dotnet-script\D\scriptB.csx\execution-cache\script.dll

Motivation and Context

I would like to benefit from the execution speed up by caching without having to separate every script into its own directory.

[filipw]

Thanks, that looks reasonable.

The folder concept is a bit complicated in scripting, because e.g. in nuget intellisense handling, package availability in OmniSharp is handled per folder. If I recall correctly, this was also a reason why caching behaves this way.

@seesharper do you have any objections to change this?

[DanielEgbers]

Interesting, I did not know about that.

I now tested my changes in combination with VSCode/OmniSharp.

Usability wise, everything seems to work normal including intellisense for nuget packages.

Technically wise, this PR only changes the location of the execution-cache.
The script project cache path (that folder named after the TargetFramework) was not changed and is therfore still directory based. VSCode/OmniSharp only seems to use this script project cache.

Temp-Folder content before this PR:

%tmp%\dotnet-script\D\execution-cache\script.dll
%tmp%\dotnet-script\D\net5.0\script.csproj
%tmp%\dotnet-script\D\net5.0\obj\
%tmp%\dotnet-script\D\net5.0\compilation\

Temp-Folder content after this PR:

%tmp%\dotnet-script\D\scriptA.csx\execution-cache\script.dll
%tmp%\dotnet-script\D\scriptB.csx\execution-cache\script.dll
%tmp%\dotnet-script\D\net5.0\script.csproj
%tmp%\dotnet-script\D\net5.0\obj\
%tmp%\dotnet-script\D\net5.0\compilation\

[DanielEgbers]

I have used a custom dotnet-script version including this change for the last 3 months. Debugging and writing (with autocomplete and so on) in VSCode works normal just like before.

@filipw can this get merged?

[seesharper]

Looks good to me. Could you just rebase this from master and we should be good to go 👍

[DanielEgbers]

I rebased it. Thanks

[seesharper]

@filipw Can you take a last look at this. I think it is good to go 👍

[filipw]

sorry for the delay - and thanks!

[mungojam]

I would guess that this fixes my issue too #540, but I probably won't get time to check