modules: update FindGLFW for MSVC 2022 17.10+.

Microsoft should fire all versioning scheme managers and then start
over. Why a single product needs

- a marketing version that's just a year number
- a major.minor.patch marketing version because the year was too coarse
  to be meaningful for anything, and that version being also completely
  unrelated to the year for good measure
- a runtime library version that used to match the major.minor marketing
  version a decade ago but then it somehow got out of sync
- a _MSC_VER macro that was in sync with the short marketing version
  last time in 1989 and never again
- an internal build number that feels like a countermeasure to "sorry,
  can't have reproducible builds so be sure to ship the artifact number
  194033811, that one we tested"

modules/FindGLFW.cmake

@@ -87,7 +87,9 @@ if(CORRADE_TARGET_WINDOWS)
             set(_GLFW_LIBRARY_PATH_SUFFIX lib-vc2017)
         elseif(MSVC_VERSION VERSION_LESS 1930)
             set(_GLFW_LIBRARY_PATH_SUFFIX lib-vc2019)
-        elseif(MSVC_VERSION VERSION_LESS 1940)
+        # MSVC 2022 17.10 overflowed the 1930 range to 1940, so assume a
+        # hypothetical MSVC 2025 will start with 1950.
+        elseif(MSVC_VERSION VERSION_LESS 1950)
             set(_GLFW_LIBRARY_PATH_SUFFIX lib-vc2022)
         else()
             message(FATAL_ERROR "Unsupported MSVC version")