util: expose diff function used by the assertion errors

[puskin94]

fix: #51740

Exporting the new util.diff(actual, expected) function.

This function is the one internally used by the assert module when an AssertionError occurs and it is just an utility to better show differences between the two params actual and expected.

It is internally using the "new" Myers diff algorithm so you can expect the same output provided by this PR: #54862

[codecov]

Codecov Report

Attention: Patch coverage is 95.65217% with 3 lines in your changes missing coverage. Please review.

Project coverage is 90.23%. Comparing base (3329efe) to head (dd09392).
Report is 49 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/internal/assert/myers_diff.js	85.71%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #57462      +/-   ##
==========================================
+ Coverage   90.20%   90.23%   +0.02%     
==========================================
  Files         629      630       +1     
  Lines      184948   184898      -50     
  Branches    36204    36217      +13     
==========================================
- Hits       166837   166834       -3     
+ Misses      11057    11019      -38     
+ Partials     7054     7045       -9     

Files with missing lines	Coverage Δ
lib/internal/util/diff.js	100.00% <100.00%> (ø)
lib/util.js	97.75% <100.00%> (+0.04%)	⬆️
lib/internal/assert/myers_diff.js	89.20% <85.71%> (+0.31%)	⬆️

... and 56 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jasnell]

Code change LGTM with one nit about the docs.

[github-actions]

The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @benjamingr.

Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section.

[pmarchini]

LGTM (only one nit)

[BridgeAR]

This looks pretty good!

I would still consider changing the output format to be the most performant one we can think of. I would likely change it to: [type, value], where type would be one of -1, 0, 1.

[BridgeAR]

Nice! This is shaping up well!

Two small things, otherwise it's LGTM

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/65806/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/65822/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/65828/

[BridgeAR]

Great work

[nodejs-github-bot]

Landed in 6b42554