nvda

89944452 - Fix beta build by better clearly distinguishing between the main nvda launcher and the l10nutil exe files (#17249)

Fix beta build by better clearly distinguishing between the main nvda launcher and the l10nutil exe files (#17249) See failed beta build: https://ci.appveyor.com/project/NVAccess/nvda/builds/50731013 Summary of the issue: NVDA's appVeyor diploy code finds the main NVDA launcher by simply matching on output*.exe. This is expected to match on a single file. However, with the introduction of the nvdaL10nUtil.exe to the output directory, the pattern also matched on this file, causing the deploy to fail. Description of user facing changes None Description of development approach * renamed nvdaL10nUtil.exe to l10nUtil.exe * Changed the pattern that locates the nvda launcher to output\nvda_*.exe. Testing strategy: This can only be tested via a successful beta build. Known issues with pull request: * It would be good if we could better calculate the main NVDA launcher name based on version type etc, but this would require a bit of careful refactoring. * had to rename nvdal10nUtil.exe to the more generic l10nUtil.exe. Documentation currently states nvdaL10nUtil.exe. Though once this is successfully building for beta, the plan is to place this util somewhere public for translators to download, and at that point we can rename that copy to nvdaL10nUtil.exe and provide clearer documentation on where to get it.