Use Unix line endings for shell scripts

[xtqqczze]

PR Summary

• Specify line ending behaviour in EditorConfig like in dotnet/runtime
• Update line endings in *.sh

PR Context

These changes fix SC1017

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
  • [NA] Experimental feature(s) needed
    • [NA] Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • [NA] Documentation needed
    • [NA] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • [NA] 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
  • [NA] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • [NA] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • [NA] Issue filed:
    • [NA] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • [NA] Issue filed:
    • [NA] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • [NA] Issue filed:
    • [NA] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • [NA] Issue filed:

[iSazonov]

We already use core.autocrlf=true in git config. So the files already have LF in repository and on Unix.
https://stackoverflow.com/questions/1967370/git-replacing-lf-with-crlf

[iSazonov]

See the history https://github.com/PowerShell/PowerShell/search?q=autocrlf&type=issues
Conclusion was to delegate this to Git autocrlf

[andyleejordan]

I agree with @iSazonov that auto-crlf in Git ought to be ensuring this already happens, but I've had issues with that working 100% (you can forcibly add files, etc., it's just not perfect), so I see no harm setting this explicitly for shell scripts.

[ghost]

Open PRs should not be assigned to milestone, so they are not assigned to the wrong milestone after they are merged. For backport consideration, use a backport label.

[xtqqczze]

The issue is that shell scripts should never contain \r\n line terminators.

https://github.com/dotnet/runtime/blob/main/.gitattributes has:
*.sh text eol=lf

Apparently if this was not the case there could be issues if a shell script was accessed in Unix via a file share from Windows.

[ghost]

🎉v7.2.0-preview.5 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes