update mocha and azdata-test versions to update debug package dependency

[kisantia]

This updates the mocha and azdata-test package versions so that the minimum dependency on the debug package is no longer one that's flagged by the dependabot alerts (ex of one of the alerts: https://github.com/microsoft/azuredatastudio/security/dependabot/605).

This is the same version of mocha that the ADS package.json currently is:

azuredatastudio/package.json

Line 234 in 5b0bafe

"mocha": "^9.2.2",

[coveralls]

Pull Request Test Coverage Report for Build 6886819235

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.001%) to 41.568%

---

Files with Coverage Reduction	New Missed Lines	%
src/sql/workbench/services/connection/browser/connectionDialogWidget.ts	1	73.44%

Totals
Change from base Build 6882746685:	-0.001%
Covered Lines:	30790
Relevant Lines:	69372

---

💛 - Coveralls

[kisantia]

There were a few strange compilation errors in the integrations-tests and notebooks extensions that seemed related to the azdata-test package bump (example error: "This comparison appears to be unintentional because the types '3' and '0' have no overlap" for an assert in notebook.test.ts, which went away if I switched it to use assert.strictEqual), so the latest change undid the azdata-test bump in those two extensions and only the mocha version is getting updated for those two. I'll look into updating those two in a separate PR so it's easier to review, since this PR already has a lot of changes.

[cheenamalhotra]

I'll look into updating those two in a separate PR so it's easier to review, since this PR already has a lot of changes.

Maybe worth opening a new issue, if it's low priority or you don't intend to do it right-away :)

[kisantia]

I'll look into updating those two in a separate PR so it's easier to review, since this PR already has a lot of changes.

Maybe worth opening a new issue, if it's low priority or you don't intend to do it right-away :)

I'm planning to look into it later today, but good idea to open a tracking issue if I don't end up getting to it :)