fix ua asserts issue without tap

[dmanto]

Summary

This PR addresses an issue with TestUserAgent where several assertion methods, such as .jsonIs(), did not work when using the native node:assert/strict module, specifically due to missing assertion methods like assert.same().

Fix

• Implemented missing assertion methods to ensure compatibility with node:assert/strict, such as replacing assert.same() with assert.deepStrictEqual() for deep equality checks.
• Updated the code to support both tap and node:assert/strict modes in the TestUserAgent to provide flexibility in testing.

Changes

• Mapped _assert methods to TestUserAgent to support the required assertions:
  • assert.equal → assert.strictEqual
  • assert.not → assert.notStrictEqual
  • assert.match → assert.match
  • assert.notMatch → assert.doesNotMatch
  • assert.ok → assert.ok
  • assert.notOk → custom implementation for negated assert.ok
  • assert.same → assert.deepStrictEqual
• Updated tests to validate assertion compatibility in both tap and node:assert/strict modes.

Caveat

This fix maps node:assert/strict methods to their tap counterparts. This could give the impression that we are prioritizing the tap API over the native node:assert API.

If preferred, we can consider making node:assert/strict the primary module for assertions in TestUserAgent and refactor the code accordingly.

[kraih]

Yes, node:assert should be the priority.

[dmanto]

Hi, just checking if you had any further feedback on this approach after the refactor prioritizing node:assert. Let me know if there's anything else you'd like me to address

[kraih]

Thanks, that seems like a reasonable solution.