.net 5 single-file deployment robustness

[haraldsteinlechner]

in introspection/plugin loading we heavily make use of assembly.location et al. This is no longer possible in .net 5 - https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly.location?view=net-5.0#remarks

the background description can be found here: https://github.com/dotnet/designs/blob/main/accepted/2020/single-file/design.md

In 5f67063 we took a first step towards this goal and made some bits generally more robust, e.g. got rid of those:

nhandled exception. System.ArgumentException: The path is empty. (Parameter 'path')
   at System.IO.Path.GetFullPath(String path)
   at System.IO.File.GetLastWriteTimeUtc(String path)
   at Aardvark.Base.CachingProperties.GetIdentifier(Assembly asm, NamingScheme scheme)
   at Aardvark.Base.Introspection.GetQueryCacheFilename(Assembly asm, Guid queryGuid)
   at Aardvark.Base.Introspection.GetAll___[T](Assembly a, String discriminator, Func`2 decode, Func`2 createResult, Func`2 encode)
   at Aardvark.Base.Introspection.GetAllMethodsWithAttribute[T](Assembly a)
   at Aardvark.Base.Aardvark.LoadAll(IEnumerable`1 xs)
   at Aardvark.Base.Aardvark.Init()
   at Program.main(String[] argv)

What remains is to find a solution which allows us to scan for potential plugin assemblies.

There are numerous projects with similar problems. Maybe we can get some information there, e.g. nuke-build/nuke#764

[hyazinthh]

Fixed this, plugin loading support was a bit tricky because you have to get the assemblies from the bundle. This library makes this easy fortunately: https://github.com/Droppers/SingleFileExtractor