Fix and Update JavaScript Recourses Links (#5896)

* Update JavaScript-asynchronous Promises resources

* Replace broken link

The previous link to the article was outdated and resulted in a 404 error.

* Fixed the JavaScript typo

* Add Video Resource JS 101-debugging-memory-leaks.md

Added a helpful YouTube video on visualizing memory leaks and debugging them in the console.

* Introduce resource (Chrome Developers) JS-debugging-performance

Added link to Chrome Developers documentation on debugging JavaScript performance in JS 102-debugging-performance.md. This provides valuable insights and best practices for optimizing code performance from the official docs.

src/data/roadmaps/javascript/content/112-javascript-asynchronous-javascript/104-promises/index.md

@@ -8,3 +8,4 @@ Visit the following resources to learn more:
 - [@article@JavaScript Promises - Basics](https://www.codeguage.com/courses/advanced-js/promises-basics)
 - [@article@JavaScript Promises - Chaining](https://www.codeguage.com/courses/advanced-js/promises-chaining)
 - [@article@JavaScript Promises - Error Handling](https://www.codeguage.com/courses/advanced-js/promises-error-handling)
+- [@video@JavaScript Promises - Visualized](https://youtu.be/Xs1EMmBLpn4)

src/data/roadmaps/javascript/content/117-javascript-chrome-dev-tools/101-debugging-memory-leaks.md

@@ -8,3 +8,4 @@ Visit the following resources to learn more:
 - [@article@Effective Javascript Debugging ](https://medium.com/swlh/effective-javascript-debugging-memory-leaks-75059b2436f6)
 - [@article@Debugging JavaScript memory leaks](https://www.debugbear.com/blog/debugging-javascript-memory-leaks)
 - [@article@Debugging Memory Leaks In Production JavaScript Applications](https://www.jackhoy.com/web-applications/2020/10/21/debugging-memory-leaks-in-nodejs.html)
+- [@video@JavaScript Memory Leaks Visualized and How To Fix Them](https://youtu.be/IkoGmbNJolo)

src/data/roadmaps/javascript/content/117-javascript-chrome-dev-tools/102-debugging-performance.md

@@ -1,3 +1,7 @@
 # Debugging performance
 
 Enter the dev tools and check out the Lighthouse tab. This is essentially a series of tests which analyses the currently open website on a bunch of metrics related to performance, page speed, accessibility, etc. Feel free to run the tests by clicking the **Analyse Page Load** button (you might want to do this in an incognito tab to avoid errors arising from extensions you're using). Once you have the results, take your time and read through them (and do click through to the reference pages mentioned alongside each test result to know more about it!)
+
+Visit the following resources to learn more:
+
+- [@article@Analyze runtime performance](https://developer.chrome.com/docs/devtools/performance)

src/data/roadmaps/javascript/content/118-working-with-apis/index.md

@@ -8,4 +8,4 @@ Visit the following resources to learn more:
 - [@article@XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest)
 - [@article@Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)
 - [@article@Is fetch API better than XMLHTTPRequest](https://medium.com/beginners-guide-to-mobile-web-development/the-fetch-api-2c962591f5c)
-- [@article@Ajax Battle: XMLHttpRequest vs the Fetch API](https://blog.openreplay.com/ajax-battle-xmlhttprequest-vs-the-fetch-api)
+- [@article@Ajax Battle: XMLHttpRequest vs the Fetch API](https://blog.openreplay.com/ajax-battle-xmlhttprequest-vs-fetch/)