### Godot version

v4.0.beta12.mono.official [3c9bf4bc2]

### System information

Windows 10, Forward+ (Vulkan), NVIDIA GeForce RTX 3070 (526.98)

### Issue description

The `Initial Screen` select dropdown provides 64 options for monitors when it should only provide options for what is available.  In my case, I'm only using two monitors so there should only be two monitors to choose from (excluding the Primary Monitor option of course).  Screenshot below.

![image](https://user-images.githubusercontent.com/1691061/213066149-b97d3220-9b23-4685-a155-ad2f48f96de3.png)


### Steps to reproduce

The issue appears to occur whether I'm using two monitors or one monitor.

---
1. Open `Project Settings`
2. Go to `Display` > `Window` > `Size`
3. Select the `Initial Screen` dropdown.
4. You will see the `Primary Monitor` option and 64 other monitor options as seen in the screenshot.

### Minimal reproduction project

N/A
}
		}
	}
}
/*
 * This method is responsible for loading a project.godot file and/or data file
 * using the following merit order:
 *  - If using NetworkClient, try to lookup project file or fail.
 *  - If --main-pack was passed by the user (`p_main_pack`), load it or fail.
 *  - Search for project PCKs automatically. For each step we try loading a potential
 *    PCK, and if it doesn't work, we proceed to the next step. If any step succeeds,
 *    we try loading the project settings, and abort if it fails. Steps:
 *    o Bundled PCK in the executable.
 *    o [macOS only] PCK with same basename as the binary in the .app resource dir.
 *    o PCK with same basename as the binary in the binary's directory. We handle both
 *      changing the extension to '.pck' (e.g. 'win_game.exe' -> 'win_game.pck') and
 *      appending '.pck' to the binary name (e.g. 'linux_game' -> 'linux_game.pck').
 *    o PCK with the same basename as the binary in the current working directory.
 *      Same as above for the two possible PCK file names.
 *  - On relevant platforms (Android/iOS), lookup project file in OS resource path.
 *    If found, load it or fail.
 *  - Lookup project file in passed `p_path` (--path passed by the user), i.e. we
 *    are running from source code.
 *    If not found and `p_upwards` is true (--upwards passed by the user), look for
 *    project files in parent folders up to the system root (used to run a game
 *    from command line while in a subfolder).
 *    If a project file is found, load it or fail.
 *    If nothing was found, error out.
 */
Error ProjectSettings::_setup(const String &p_path, const String &p_main_pack, bool p_upwards, bool p_ignore_override) {