repl: fix multiline history editing string order

[puskin94]

fixing an issue introduced in the last commit of #57400:
when editing a multiline history in REPL, the string gets reversed.

Added relevant automated tests

[BridgeAR]

Would this also fix the flaky behavior reported in the comment? :)

#57400 (comment)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.24%. Comparing base (f89baf2) to head (03cd310).
Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #57874      +/-   ##
==========================================
- Coverage   90.24%   90.24%   -0.01%     
==========================================
  Files         630      630              
  Lines      185670   185694      +24     
  Branches    36401    36404       +3     
==========================================
+ Hits       167567   167577      +10     
- Misses      10992    10999       +7     
- Partials     7111     7118       +7     

Files with missing lines	Coverage Δ
lib/internal/readline/interface.js	96.79% <100.00%> (+0.01%)	⬆️

... and 37 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.

[puskin94]

Would this also fix the flaky behavior reported in the comment? :)

#57400 (comment)

I just added some code which could fix the flakiness... I am not sure if it is good / clean enough tho, I didn't have any cooler idea 😞

[BridgeAR]

I don't think the wait should make a difference for the test being flaky. I could imagine we run tests in parallel that use the same repl file to write to and they conflict with each other. Or is that unique to the current tmp directory?

The flaky result said we had two history entries.

[puskin94]

Yeah I interpreted the two history entries as in a weird combination of keypresses which were not properly "awaited" for. Unfortunately I cannot reproduce the issue, let me investigate the "multiple access to the same history file" path

EDIT: applied your suggestion, let's see if it happens again!

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

Landed in af85f3f