Allow compatible newer Fonts and Admin dependency versions

[MariusStorhaug]

Context and request

Install-GoogleFont.ps1 currently declares exact dependency pins:

#Requires -Modules @{ ModuleName = 'Fonts'; RequiredVersion = '1.1.21' }
#Requires -Modules @{ ModuleName = 'Admin'; RequiredVersion = '1.1.6' }

RequiredVersion rejects newer compatible releases. A user with a newer Fonts or Admin version may therefore be unable to import GoogleFonts unless the historical exact version is also installed.

Desired outcome

Use compatible version ranges instead of exact pins so newer supported dependency releases satisfy module import requirements.

Acceptance criteria

• GoogleFonts imports when installed Fonts and Admin versions meet or exceed its required compatible minimums.
• The function requirements use ModuleVersion and, if a major-version compatibility boundary is needed, MaximumVersion; they do not use RequiredVersion for these published dependencies.
• The README states the supported dependency range rather than an exact historical version.
• Tests cover both the minimum supported and a newer compatible dependency version.

Related

• Fix module import failure when newer Admin or Fonts versions are installed NerdFonts#64 documented the same import failure. Its current implementation uses a minimum version plus a 1.* maximum boundary.
• Fix module import failure when a newer Admin version is installed Fonts#58 and 🪲 [Fix]: Module import no longer fails when a newer Admin version is installed Fonts#59 addressed the equivalent dependency issue in the Fonts module.