Support for chained conditional expressions about fluentassertions.analyzers

[Meir017]

ok, so, for now, I will just add support for a smarter analyzer without a code fix

[Meir017]

So basically using a null conditional expression together with the Should method should trigger the analyzer?

I was thinking about adding a code-fix that will recommend removing the null conditional expression, does this make sense?

[jnyrup]

I think using conditional expressions on the left hand side of Should should trigger the analyzer.
The conditional expression makes the assertion unclear - at least to me.

I had a unit test the other day like this

actual?.Property.Should().NotBeNull();

where I think the intention was to check that both actual and Property should not be null.

So I rewrote it into

actual.Should().NotBeNull();
actual.Property.Should().NotBeNull();

So I can't come up with a good code-fix, I guess it depends whether you would just remove the ?, split it into two assertions or something else.

[Meir017]

added more tests for NullConditionalAssertionAnalyzer 6b87da0