Normalize query workbench constant newlines

[Swiddis]

Description

When running integration tests on windows, the CSV data inconsistently was encoded with \r\n or \n, which caused a failing test assertion. This PR adds a method to normalize the test data.

Issues Resolved

N/A

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[SuZhou-Joe]

Need backport main or 2.x?

[Swiddis]

Yes, will also need backports, just starting here in reaction to failing RC tests.

Just saw it was already merged and backported, thanks 👍

[ps48]

@wanglam @SuZhou-Joe Can we please backport this change to 1.3 branch. This PR fixes the issue for our windows test failures the 1.3.15 release.

[opensearch-trigger-bot]

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-1105-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 842fe0ccc120b79337642c6c4c762453b8ec838d
# Push it to GitHub
git push --set-upstream origin backport/backport-1105-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-1105-to-1.3.

[wanglam]

@Swiddis @ps48 Seems automatic backport failed for 1.3 branch. Need manual backport.