Fix wxThread::SetPriority() documentation

The documentation's notes about MSW limitations about setting priority
before creating the thread do not appear to be true (anymore). Thread
priority is already set by Create() if SetPriority() was called earlier.
Setting it immediately just failed, because the thread did not exist
yet, but this was fixed by the previous commit.

include/wx/thread.h

@@ -559,9 +559,6 @@ public:
     // priority
         // Sets the priority to "prio" which must be in 0..100 range (see
         // also wxPRIORITY_XXX constants).
-        //
-        // NB: under MSW the priority can only be set after the thread is
-        //     created (but possibly before it is launched)
     void SetPriority(unsigned int prio);
 
         // Get the current priority.

interface/wx/thread.h

@@ -1267,11 +1267,6 @@ public:
           - @c wxPRIORITY_DEFAULT: 50
           - @c wxPRIORITY_MAX: 100
 
-        Notice that in the MSW implementation the thread priority can currently
-        be only set after creating the thread with CreateThread(). But under
-        all platforms this method can be called either before launching the
-        thread using Run() or after doing it.
-
         Please note that currently this function is not implemented when using
         the default (@c SCHED_OTHER) scheduling policy under POSIX systems.
     */