CONTRIBUTING

debugfs: display the tested path and mount point of the filesystem, if known

While implementing win32.getfstype(), I noticed that MSYS path mangling is
getting in the way.  Given a path \\host\share\dir:

  - If strong quoted, hg receives it unchanged, and it works as expected
  - If double quoted, it converts to \host\share\dir
  - If unquoted, it converts to \hostsharedir

The second and third cases are problematic because those are valid paths
relative to the current drive letter, so os.path.realpath() will expand it as
such.  The net effect is to silently turn a network path test into (typically) a
"C:\" test.  Additionally, the command hangs after printing out 'symlink: no'
for the third case (but is interruptable with Ctrl + C).  This path mangling
only comes into play because of the command line arguments- it won't affect
internally obtained paths.  Therefore, the simplest thing to do is to provide
feedback on what the command is acting on.

I also added the mount point, because Windows supports nesting [1] volumes (see
the examples in "Junction Points and Mounted Folders"), and it was a useful
diagnostic for figuring out why the wrong filesystem was printed out in the
cases above.

I opted not to call os.path.realpath() on the path argument, to make it clearer
that the mangling isn't being done by Mercurial.

[1] https://msdn.microsoft.com/en-us/library/windows/desktop/aa364996(v=vs.85).aspx

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).