Allow requesting a larger paging file on Windows shared runners
Description
There's no easy way to build a native installer for Windows (msi) for Java applications on the GitLab CI/CD infrastructure. The "modern" way to do so is using jpackage (which uses jlink), but jlink can't run on the Windows runners because the paging file is too small. You can either run it locally, which defeats the purpose of the build stage in the pipeline or try to jlink on a Linux runner (but then you have to somehow provide a Windows JDK).
Proposal
Allow a YAML element to request a larger paging file size for the Windows shared runners. CircleCI for instance has a resource_class attribute in their YAML config for executors, which allows to request a certain number of virtual CPUs and amount of RAM (not exactly what I'm talking about but maybe something similar for the paging file could be done). It would probably complicate things, but it would be possible to charge more for a larger paging file I suppose.