RFR: 8348828: Windows dll loading now resolves symlinks [v3]

[Benjamin Peterson]

> Deep in the bowels of `System.loadLibrary`, `File.getCanonicalPath()` is called on the target library file before it is passed to the system library loading APIs. In JDK-8003887, `File.getCanonicalPath` was altered to resolve symlinks on Windows. This had unintended consequences for passing a symlink to `System.loadLibrary` on Windows. The underlying Windows `LoadLibrary` API inspects the file name passed to it and adds a `.dll` extension if the it is not already present. Thus, if `System.loadLibrary` was given a symlink to a file and that file didn't have a `.dll` extension, `LoadLibrary` try to load nonexistent file and fail.
> 
> Fix this problem by appending a `.` to library paths after canonicalization on Windows. This trailing dot inhibits `LoadLibrary`'s own appending behavior.

Benjamin Peterson has updated the pull request incrementally with one additional commit since the last revision:

  fix spelling

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/24694/files
  - new: https://git.openjdk.org/jdk/pull/24694/files/f16626be..70e943c8

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=24694&range=02
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=24694&range=01-02

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/24694.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/24694/head:pull/24694

PR: https://git.openjdk.org/jdk/pull/24694