Use Navigation.goBack instead of navigate after agent deletion

After deleting an agent, the app was pushing a new Agents list screen
onto the navigation stack instead of popping back to the existing one.
This caused the back button to return to the stale Edit Agent page.

Co-authored-by: Nicolás Bonet <NicolasBonet@users.noreply.github.com>

Author: MelvinBot

src/libs/actions/Agent.ts

@@ -282,7 +282,7 @@ function deleteAgent(accountID: number) {
     ];
 
     write(WRITE_COMMANDS.DELETE_AGENT, {agentAccountID: accountID}, {optimisticData, successData, failureData});
-    Navigation.navigate(ROUTES.SETTINGS_AGENTS);
+    Navigation.goBack(ROUTES.SETTINGS_AGENTS);
 }
 
 export {

tests/unit/AgentActionTest.ts

@@ -8,10 +8,10 @@ import ONYXKEYS from '@src/ONYXKEYS';
 import type {AnyOnyxUpdate} from '@src/types/onyx/Request';
 
 jest.mock('@libs/API');
-jest.mock('@libs/Navigation/Navigation', () => ({navigate: jest.fn()}));
+jest.mock('@libs/Navigation/Navigation', () => ({navigate: jest.fn(), goBack: jest.fn()}));
 
 const mockWrite = jest.mocked(write);
-const mockNavigate = jest.mocked(Navigation.navigate);
+const mockGoBack = jest.mocked(Navigation.goBack);
 
 function getWriteOptions(): {optimisticData: AnyOnyxUpdate[]; successData: AnyOnyxUpdate[]; failureData: AnyOnyxUpdate[]} {
     const options = mockWrite.mock.calls.at(0)?.at(2);
@@ -386,10 +386,10 @@ describe('deleteAgent', () => {
         expect((promptUpdate?.value as Record<string, unknown>)?.errors).toBeTruthy();
     });
 
-    it('calls Navigation.navigate after issuing the write', () => {
+    it('calls Navigation.goBack after issuing the write', () => {
         deleteAgent(TEST_ACCOUNT_ID);
 
-        expect(mockNavigate).toHaveBeenCalledTimes(1);
+        expect(mockGoBack).toHaveBeenCalledTimes(1);
     });
 });