Plugin doesn't work if no apollo project at first place in workspace

Type: Bug

Let's say you have several projects in your workspace using apollo.config.js.

If none of them is in first position, the plugin is disabled and you'll have errors spawning about loading schemas and initializing Apollo GraphQL projects.

But as soon as you place one of the apollo projects in first place, the plugin is re-enabled.

Extension version: 1.19.11
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:32:21.587Z)
OS version: Darwin arm64 22.2.0
Modes:
Sandboxed: No

System Info

|Item|Value|
|---|---|
|CPUs|Apple M1 (8 x 24)|
|GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off|
|Load (avg)|4, 3, 3|
|Memory (System)|16.00GB (0.05GB free)|
|Process Argv|--crash-reporter-id 53a2c80b-8303-4272-b837-bc49d98b344e|
|Screen Reader|yes|
|VM|0%|

┆Issue is synchronized with this [Jira Task](https://apollographql.atlassian.net/browse/NEBULA-2042) by [Unito](https://www.unito.io)

Reproduce the issue with a multi-root VS Code workspace where an Apollo project is not first, then trace the extension's workspace project discovery and initialization flow. Done means the plugin stays enabled and no schema-loading or Apollo project initialization errors appear regardless of folder order.

Written by the indexing model from the issue text.