Fixed bug: race condition and memory leak in useEffect data fetching

[hemannt003]

**Fixed bug: race condition and memory leak in useEffect data fetching **

This PR fixes #157

What I changed

• Updated webapp/src/components/Stack/Stack.jsx
• Updated webapp/src/components/GdbComponents/BreakPoints/BreakPoints.jsx Updated webapp/src/components/Functions/Functions.jsx Updated webapp/src/components/GdbComponents/MemoryMap/MemoryMap.jsx Also updated webapp/src/components/Terminal/TerminalComp.jsx after searching for other useEffect-triggered API requests

Fix pattern applied

For each affected useEffect with API calls:

• Created a new AbortController per effect run
• Passed signal into the request (axios.post(..., { signal }))
• Added cleanup return () => controller.abort() to cancel in-flight request on dependency change/unmount
• Guarded state updates with if (!signal.aborted) so aborted/stale responses cannot update UI
• Ignored abort/cancel errors (AbortError / CanceledError / ERR_CANCELED) and only logged real failures

Result

• Prevents delayed older responses from overwriting newer state
• Prevents state updates after unmount (memory leak warning case)
• Keeps existing UI behavior and state shape unchanged (only fetching logic was touched)

[hemannt003]

Hi @Shubh942 Could you please review the PR whenever you get time and let me know for any changes to be made.