Ensure ForwardCancellationTokenAnalyzer treats usages of default expressions properly

[DavidBoike]

Backports the following to the release-8.0 branch.

• Fix ForwardCancellationTokenAnalyzer bug on default parameter values #6616

---

This fixes a bug discovered in the ForwardCancellationTokenAnalyzer and adds several more test cases.

The analyzer is supposed to ignore when you pass CancellationToken.None, but throwing an exception when doing the same thing but by using a default operator or literal which were introduced between C# 7 and 8:

// OK
await Task.Delay(100, CancellationToken.None);

// Throwing exceptions in 8.0.0
await Task.Delay(100, default(CancellationToken));
await Task.Delay(100, default);

This requires better analysis to make sure the presence of default doesn't throw it off:

public async Task SomeMethod(int a, string b, CancellationToken token = default) { }

// Would pass the 0 and null but not provide a token:
await SomeMethod(default, default);

This PR also introduces several test cases around the use of await foreach… when using async enumerables.

---

Symptoms

During development, the following compiler warning is observed:

AD0001: Analyzer 'NServiceBus.Core.Analyzer.ForwardCancellationTokenAnalyzer' threw an exception of type 'System.IndexOutOfRangeException' with message 'Index was outside the bounds of the array.'

Who's affected

Anyone using NServiceBus 8.0.0 attempting to analyze code that passes default(CancellationToken) or default for a CancellationToken parameter is affected.

Root cause

The root cause is a bug in an NServiceBus analyzer which was not expecting one of the default expressions to be used.