fix: Bitbucket fetcher test had unused code

[wulmer]

Hi @einnhverr , one of the Bitbucket tests had some braces/indentation issue, please have a look at my fix.

[github-actions]

Code Coverage Report

Project	Statements Rate	Branch Rate	Indicator
packages/autopilot-utils	96.67%	90.23%	💚
dist/coverage/python	96.67%	90.23%	💚
apps/splunk-fetcher	92.51%	82.00%	💚
apps/sharepoint-fetcher	84.83%	76.62%	💚
apps/sharepoint-evaluator	94.09%	90.48%	💚
apps/sharepoint	83.98%	67.86%	💚
apps/security-scanner	0.00%	0.00%	💔
apps/pex-tool	93.07%	78.05%	💚
apps/pdf-signature-evaluator	67.48%	48.80%	💛
apps/papsr	98.25%	94.74%	💚
apps/filecheck	98.53%	96.30%	💚
apps/excel-tools	78.37%	62.89%	💛
apps/artifactory-fetcher	98.51%	92.86%	💚
Total	87.13%	75.70%	💚

[einnhverr]

LGTM.
I would recommend to also change to non-aliased API calls, e.g.toBeCalledWith() -> toHaveBeenCalledWith(). Since Vitest is tracking Jest APIs, and it appears there are plans to be removed in the future

[wulmer]

LGTM. I would recommend to also change to non-aliased API calls, e.g.toBeCalledWith() -> toHaveBeenCalledWith(). Since Vitest is tracking Jest APIs, and it appears there are plans to be removed in the future

Thanks for the hint. I consider this out of scope for now, but sooner or later, someone has to deal with it.