Concurrency: fix UB in DefaultActor initialization

This fixes a latent UB instance in the `DefaultActor` implementation
that has haunted the Windows target.  The shared constructor for the
type caused an errant typo that happened to compile which introduced
UB but happened to work for the non-Windows cases.  This happened to
work for the other targets as `swift::atomic` had a `std::atomic` at
on most configurations, and the C delegate for the Actor initializer
happened to overlap and initialize the memory properly.  The Windows
case used an inline pointer width value but would be attempted to be
initialized as a `std::atomic`.  Relying on the overlap is unsafe to
assume, and we should use the type's own constructor which delegates
appropriately.

Author: compnerd

stdlib/public/Concurrency/Actor.cpp

@@ -698,7 +698,7 @@ class DefaultActorImpl : public HeapObject {
   void initialize(bool isDistributedRemote = false) {
     auto flags = Flags();
     flags.setIsDistributedRemote(isDistributedRemote);
-    new (&CurrentState) std::atomic<State>(State{JobRef(), flags});
+    new (&CurrentState) swift::atomic<State>(State{JobRef(), flags});
     JobStorageHeapObject.metadata = nullptr;
   }
 

test/Distributed/Runtime/distributed_actor_dynamic_remote_func.swift

@@ -7,9 +7,6 @@
 // UNSUPPORTED: use_os_stdlib
 // UNSUPPORTED: back_deployment_runtime
 
-// FIXME(distributed): remote functions dont seem to work on windows?
-// XFAIL: OS=windows-msvc
-
 import _Distributed
 
 distributed actor LocalWorker {

test/Distributed/Runtime/distributed_actor_isRemote.swift

@@ -8,9 +8,6 @@
 // UNSUPPORTED: use_os_stdlib
 // UNSUPPORTED: back_deployment_runtime
 
-// FIXME(distributed): remote functions dont seem to work on windows?
-// XFAIL: OS=windows-msvc
-
 import _Distributed
 
 @available(SwiftStdlib 5.6, *)