Bug: router crate fails to build in WSL unless more memory is added



I am part of a student team hoping to contribute to hyperswitch over the next several months. After following the instructions in `docs/try_local_system.md` for setting up a development environment using WSL, all members of my team encountered the same issue: upon running `cargo build`, the `router` crate failed to build, producing an error ending in `signal: 9, SIGKILL: kill`.

After some research, we came across [this discussion post](https://github.com/juspay/hyperswitch/discussions/758), where the author encountered a similar issue. After trying the suggested solution of configuring WSL to allow an additional 2GB of memory, the issue persisted, however we were able to resolve it by increasing the amount to 24GB.

Some of our machines do not have 24GB of memory, so we ended up editing `.wslconfig` to include 8GB of memory, and then adding an additional 16GB via a swap file created from within the WSL terminal.

Because the same issue occurred for all of us in the exact same way, across different machines, we feel that `docs/try_local_system.md` should mention the issue, along with instructions on how to configure WSL to prevent the issue from occurring.
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
This pull request adds a brief note to `docs/try_local_system.md`, under the section titled "Set up dependencies on Windows (Ubuntu on WSL2)," addressing an error that may occur when running `cargo build` from a WSL environment, and providing resources to help the user prevent the issue from occurring.

Additionally, I added a note about this change to `CHANGELOG.md`.

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->
closes #4432


## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [ ] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable
