Fix: Use goBack instead of navigate to prevent 404 staying in history

Navigation.navigate(ROUTES.HOME) was pushing HOME onto the navigation
stack, leaving the 404 page in browser history. Using goBack(ROUTES.HOME)
instead leverages the replace semantics in goUp(), removing the 404
from history before navigating to HOME.

Co-authored-by: truph01 <truph01@users.noreply.github.com>

Author: MelvinBot

src/pages/ErrorPage/NotFoundPage.tsx

@@ -32,7 +32,7 @@ function NotFoundPage({onBackButtonPress = () => Navigation.goBack(), isReportRe
         >
             <FullPageNotFoundView
                 shouldShow
-                onLinkPress={() => Navigation.navigate(ROUTES.HOME)}
+                onLinkPress={() => Navigation.goBack(ROUTES.HOME)}
                 onBackButtonPress={() => {
                     if (!isReportRelatedPage || !isSmallScreenWidth) {
                         onBackButtonPress();