Upload bin dir fir windows_dotnet_build

Commit 6ede47a asked:

> Will it work?

Lol, no.  No it does not:

	SetUp failed for test fixture Java.InteropTests.TestTypeTests
	System.TypeInitializationException : The type initializer for 'Java.InteropTests.JavaVMFixture' threw an exception.
	  ----> System.BadImageFormatException : An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
	   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
	   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
	   at NUnit.Framework.Internal.Reflect.Construct(Type type, Object[] arguments)
	   at NUnit.Framework.Internal.TypeWrapper.Construct(Object[] args)
	   at NUnit.Framework.Internal.Commands.ConstructFixtureCommand.<.ctor>b__0_0(TestExecutionContext context)
	   at NUnit.Framework.Internal.Commands.BeforeTestCommand.Execute(TestExecutionContext context)
	   at NUnit.Framework.Internal.Execution.CompositeWorkItem.PerformOneTimeSetUp()
	--BadImageFormatException
	   at Java.Interop.NativeMethods.java_interop_jvm_load_with_error_message(String path, IntPtr& message)
	   at Java.Interop.JreRuntime.CreateJreVM(JreRuntimeOptions builder) in D:\a\1\s\src\Java.Runtime.Environment\Java.Interop\JreRuntime.cs:line 97
	   at Java.InteropTests.TestJVM..ctor(String[] jars, Dictionary`2 typeMappings) in D:\a\1\s\tests\TestJVM\TestJVM.cs:line 61
	   at Java.InteropTests.JavaVMFixture.CreateJavaVM() in D:\a\1\s\tests\Java.Interop-Tests\Java.Interop\JavaVMFixture.cs:line 15
	   at Java.InteropTests.JavaVMFixture..cctor() in D:\a\1\s\tests\Java.Interop-Tests\Java.Interop\JavaVMFixture.Partial.cs:line 12

…which is rather odd, actually; *why* `BadImageFormatException`?

A plausible reason is that the "bitness" doesn't match, e.g. `dotnet`
is 32-bit while `java-interop.dll` is 64-bit (or vice versa).

The easiest way to tell is to download the built artifacts to see what
they actually contain.

Add a `PublishPipelineArtifact@` invocation so that we *can* download.

Author: jonpryor

build-tools/automation/azure-pipelines.yaml

@@ -93,6 +93,13 @@ jobs:
     parameters:
       runNativeTests: true
 
+  - task: PublishPipelineArtifact@1
+    displayName: Publish `bin` folder
+    inputs:
+      targetPath: bin
+      artifactName: bin-dotnet
+    condition: succeededOrFailed()
+
   - template: templates\fail-on-issue.yaml
 
 - job: mac_build