RCS1140 - Don't require user to document exception types if caught in same method

[Qluxzz]

There was no tests for RCS1140 so I added one based on the documentation for the rule.

When I was testing this rule I was not expecting it to require me to document exception types thrown but caught in the same method.

An example from a unit test I created

public void Foo(object parameter)
{
    try 
    {
        if (parameter == null)
            throw new ArgumentNullException(nameof(parameter));
    }
    catch (ArgumentNullException) {}
}

Here the exception is caught in the method but the analyzer for RCS1140 still require it to be documented on the method.

This PR checks if the exception type thrown in the method is also caught in the same method, and then removes the requirement to document it for the method.

[Qluxzz]

@dotnet-policy-service agree

[josefpihrt]

Please update changelog.

[josefpihrt]

Great PR! Thanks for the contribution.