* [System] Make FileSystemWatcher backend non-static
The FileSystemWatcher `watcher` field is the backend IFileWatcher that's
supposed to be used for the actual operations.
Each backend has a `bool GetInstance (out watcher)` method that returns a
singleton object, so each new instance of FileSystemWatcher gets the same
IFileWatcher instance. (They will get different `watcher_handle` instances
which are used by some backends to uniquely identify this FileSystemWatcher).
However when the first FileSystemWatcher instance is `Dispose`d, it will set
`watcher = null` which will prevent the remaining instances from calling
watcher?.StopDispatching (watcher_handle);
watcher?.Dispose (watcher_handle);
which means that the backend won't properly cleanup resources for any other FSW
instances that have other `watcher_handle` values.
Addresses https://github.com/mono/mono/issues/16709
While working on PR #11829 I stress-tested the tests by running multiple test
runs in parallel, and it turned out that many tests were not parallel-safe,
because they used the same temporary file names and ended up stomping on
eachother.
So I implemented a helper method that creates a guaranteed unique temporary
directory, and I've changed all tests to use this new helper method.
* System.dll.sources: added new files.
* System_test.dll.sources: added new test.
* System.IO/DefaultWatcher.cs: stub for the default watcher.
* System.IO/WindowsWatcher.cs: stub for the windows watcher.
* System.IO/FAMWatcher.cs: FAM watcher.
* System.IO/FileAction.cs: enum with event types.
* System.IO/FileSystemEventArgs.cs: added SetName property.
* System.IO/FileSystemWatcher.cs: added support for the 3 watchers.
* System.IO/IFileWatcher.cs: interface implemented by the watchers.
* System.IO/SearchPattern.cs: copied from corlib.
* Test/System.IO/FileSystemWatcherTest.cs: new test.
svn path=/trunk/mcs/; revision=22139