Native dependency unpacking not robust when switching architecture

[haraldsteinlechner]

This is a corner-case when different processor architectures are used in the same system (which is not that of a rare case on apple silicon macs). Native dependency unpacking will unpack the current architecture, the next run will skip unpacking since the target library is already there leading to dlopen failures when switching between architectures (which can happen accidentally).
See:

aardvark.base/src/Aardvark.Base/Introspection/Introspection.cs

Line 1389 in 89e5d12

if (!File.Exists(outputPath))

My suggestion is to add the architecture to the directory name (as opposed to just the library name). Does somebody see problems with this approach?