Move the WSL2 guide from getting-started/ to development/

Previously, engineers by default were only provisioned a Windows state laptop. The WSL2 was helpful as a default option for getting setting up to make this Windows laptop mimic a UNIX system as much as possible.

Today, engineers are also provisioned a Macbook to by default enable development on a UNIX system. Mimicing a UNIX system is thus no longer the default use case for using the Windows machine - engineers may instead e.g. use the Windows machine to mirror the development environment of agency partners (who may not have admin access, and would instead [develop on native Windows](https://newjersey.github.io/innovation-engineering/guides/development/node-on-native-windows/) without WSL2).

This commit thus moves the WSL2 guide from "getting started" to "development", where the sibling native windows guide in the "development" folder might better enable engineers to discover both options and consider which works better for them.

Author: josephine-njooi

src/content/docs/guides/development/node-on-native-windows.md

@@ -2,7 +2,7 @@
 title: Running a Node project on native Windows
 ---
 
-E.g., you might have agency partners working on Windows machines, and want to have them run a node project without [going through WSL2](https://newjersey.github.io/innovation-engineering/guides/laptop-setup-windows/), which requires admin access that agency partners may not have. See [this Microsoft guide](https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows) for considerations about whether to use WSL2, or native windows.
+E.g., you might have agency partners working on Windows machines, and want to have them run a node project without [going through WSL2](/innovation-engineering/guides/development/windows-wsl2-setup/), which requires admin access that agency partners may not have. See [this Microsoft guide](https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows) for considerations about whether to use WSL2, or native windows.
 
 ## Node on native Windows
 

…/getting-started/laptop-setup-windows.md …guides/development/windows-wsl2-setup.mdsrc/content/docs/guides/getting-started/laptop-setup-windows.md renamed to src/content/docs/guides/development/windows-wsl2-setup.md src/content/docs/guides/getting-started/laptop-setup-windows.md renamed to src/content/docs/guides/development/windows-wsl2-setup.md

@@ -9,4 +9,4 @@ When setting up a new OOI Macbook, use the [nj-laptop-setup](https://github.com/
 
 The README there contains all relevant information for how to run the scripts, and what to change (or not).
 
-Developing on Windows? Follow our [laptop setup guide for Windows](/innovation-engineering/guides/getting-started/laptop-setup-windows) instead.
+Developing on Windows? Follow our [laptop setup guide for Windows](/innovation-engineering/guides/development/windows-wsl2-setup) instead.

src/content/docs/guides/getting-started/laptop-setup.md

@@ -6,7 +6,7 @@ title: Setup
 
 Read our [Slack channel reference](/innovation-engineering/onboarding/6-slack) and ensure you are added to all appropriate channels.
 
-In the [GitHub Slack integration](https://github.com/settings/reminders), check the box for **"Enable real-time alerts for pull requests"**. This will give you notifications when assigned to a PR or when someone replies to your comment, and is necessary for our GH Action PR workflow. 
+In the [GitHub Slack integration](https://github.com/settings/reminders), check the box for **"Enable real-time alerts for pull requests"**. This will give you notifications when assigned to a PR or when someone replies to your comment, and is necessary for our GH Action PR workflow.
 
 ## Calendar
 
@@ -23,8 +23,7 @@ Read our [engineering meeting reference](/innovation-engineering/onboarding/7-me
 
 ## Laptop & development setup
 
-Reference our guides to setup an [OOI macbook](/innovation-engineering/guides/getting-started/laptop-setup) or a [state Windows laptop](/innovation-engineering/guides/getting-started/laptop-setup-windows)
-
+Reference our guides to setup an [OOI macbook](/innovation-engineering/guides/getting-started/laptop-setup) or a [state Windows laptop](/innovation-engineering/guides/development/windows-wsl2-setup)
 
 ## Development tools
 

src/content/docs/onboarding/5-setup.md

@@ -41,7 +41,7 @@ For Debian/Ubuntu and [WSL](https://docs.google.com/document/d/1q5InFbTTOrY_lZ5U
 curl -fsSL https://get.docker.com/ | sh
 ```
 
-Docker Engine can still be easily installed on Linux without Docker Desktop. For Windows machines (e.g. agency stakeholders), we suggest using WSL (see [Setting up a state Windows laptop](https://newjersey.github.io/innovation-engineering/guides/laptop-setup-windows/)), which can be harangued into running containers using the Docker engine on Linux.
+Docker Engine can still be easily installed on Linux without Docker Desktop. For Windows machines (e.g. agency stakeholders), we suggest using WSL (see [Setting up a state Windows laptop](/innovation-engineering/guides/development/windows-wsl2-setup/)), which can be harangued into running containers using the Docker engine on Linux.
 
 ## Infrastructure as Code