assert: optimize partial comparison of two Sets

[aduh95]

We can skip the conversion to an array of the expected items as we're only iterating over them. Using a labelled continue should also slightly improve perf as we no longer need to keep a found boolean value and check its value.
I'm also removing the TODO that no longer applies (I suggested adding it when there were plans for a assert.includes method in the PR which have since been abandoned). Lastly I'm using the SafeSet methods to iterate over the Set instances to be consistent with how we iterate over Map instances just a few lines above.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.00%. Comparing base (d0d5209) to head (9bc3511).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #55970      +/-   ##
==========================================
- Coverage   88.00%   88.00%   -0.01%     
==========================================
  Files         653      653              
  Lines      188091   188083       -8     
  Branches    35946    35949       +3     
==========================================
- Hits       165526   165517       -9     
+ Misses      15739    15732       -7     
- Partials     6826     6834       +8     

Files with missing lines	Coverage Δ
lib/assert.js	99.01% <100.00%> (-0.01%)	⬇️

... and 29 files with indirect coverage changes

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[nodejs-github-bot]

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