Fix for issue #9284 - Escape fields that contain quotes and newlines, not just those that contain the delimiter

PR Summary

This PR fixes the case of CSV fields that include double quotes or newlines in their values. If a Column value contains ",\r,\n or the delimiter then it will be marked as needing to be surrounded by quotes.

This follows RFC-4180 rules as to what characters trigger a field to be quoted (except it allows for different delimiters than the comma). This also follows how ConvertFrom-Csv parses input CSV files.

PR Context

-UseQuotes AsNeeded currently only looks for delimiters, which means that the field Hello,World will be surrounded in quotes, however the field Hello"World would not be surrounded in quotes, causing this kind of embarassing slip-up:

$testObj = [pscustomobject]@{ Greet = "Hello"; Me = "`""; Here = "World" };
# Greet Me Here
# ----- -- ----
# Hello "  World

$str = $testObj | convertto-csv -UseQuotes AsNeeded
# Greet,Me,Here
# Hello,",World  <-- Should be 'Hello,"""",World'

$str | convertfrom-csv
# Greet Me     Here
# ----- --     ----
# Hello ,World

Newlines are another risk, since they're interpreted as completely different rows.

$testObj = [pscustomobject]@{ FirstColumn = "Hello"; SecondColumn = "World`r`nGoodbye" }
FirstColumn,SecondColumn
Hello,World
Goodbye

Performance Caveat: This version is searching for the existence of 4 characters (using string.IndexOfAny(chars) instead of the original 1 (string.Contains(char). Based on my benchmarks this change does have a miniscule increase in time for that single operation. However, in my naïve in-memory benchmarks against a 100MB CSV file, using -UseQuotes AsNeeded was slightly faster than -UseQuotes Always or -QuoteFields. My guess is that I didn't need to allocate as much memory for those unneeded quotes.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed: 7796
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: