fix(test): restore Azure DevOps and Bitbucket remote-url probe assertions (#12080)

#12065 started passing an AbortSignal as a third argument to provider.exec
in readRemoteUrl, and updated the Gitea, GitHub and GitLab assertions to
match. Azure DevOps and Bitbucket were missed, so main is red on three
test files.

Same expect.any(AbortSignal) shape #12065 used for the other providers.

Co-authored-by: Orca <help@stably.ai>

src/main/azure-devops/pull-request-creation.test.ts

@@ -130,7 +130,9 @@ describe('Azure DevOps pull request creation', () => {
       ok: true,
       number: 38
     })
-    expect(remoteGit.exec).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/remote/repo')
+    expect(remoteGit.exec).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/remote/repo', {
+      signal: expect.any(AbortSignal)
+    })
     expect(gitExecFileAsyncMock).not.toHaveBeenCalled()
   })
 

src/main/azure-devops/repository-ref.test.ts

@@ -118,7 +118,9 @@ describe('parseAzureDevOpsRepoRef', () => {
       webBaseUrl: 'https://dev.azure.com/acme/Project/_git/repo'
     })
 
-    expect(sshExecMock).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/repo')
+    expect(sshExecMock).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/repo', {
+      signal: expect.any(AbortSignal)
+    })
     expect(gitExecFileAsyncMock).not.toHaveBeenCalled()
   })
 

src/main/bitbucket/repository-ref.test.ts

@@ -157,7 +157,9 @@ describe('Bitbucket repository refs', () => {
       repoSlug: 'project'
     })
 
-    expect(sshExecMock).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/repo')
+    expect(sshExecMock).toHaveBeenCalledWith(['remote', 'get-url', 'origin'], '/repo', {
+      signal: expect.any(AbortSignal)
+    })
     expect(gitExecFileAsyncMock).not.toHaveBeenCalled()
   })