Update for null-forgiving operator at end of line

[EdwinEngelen]

This falsely triggers SA1003 on the null-forgiving operator at the end of the line.

public void Foo(string? maybeNullString)
{
    var result = maybeNullString!
        .ToString();
}

Method chaining is a common practice and placing each method call on a separate line is clean. When a null-forgiving operator is applied, then it should be placed immediately after the expression that can be null. So that's at the end of the line, and not at the beginning of the next line.

Depends on PR #4077 (a stack of pull requests that together produce a NuGet package that solves my StyleCop problems).

[codecov]

Codecov Report

❌ Patch coverage is 99.26471% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.61%. Comparing base (673de60) to head (333386c).
⚠️ Report is 11 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #4080    +/-   ##
========================================
  Coverage   94.60%   94.61%            
========================================
  Files        1026     1029     +3     
  Lines      119110   119245   +135     
  Branches     3475     3480     +5     
========================================
+ Hits       112684   112820   +136     
  Misses       5366     5366            
+ Partials     1060     1059     -1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sharwell]

Marking as draft for now due to dependency on #4077