ChainedMethodInvocationRefactor should be able to handle chains of arbitrary length

[RadikalJin]

Describe the bug
The ChainedMethodInvocationRefactor will currently match on two chained method invocations, and swap them to a different method.

For example,
getCurrentFoo().doFooThing()
can be swapped to
doBarThing()

Expected behavior
This refactor should be updated so that:

• Chains of arbitrary length can be matched
• Those chains can themselves be replaced by other chains of arbitrary length, rather than just one method invocation.

For example,
getCurrentFoo()
or
getCurrentFoo().doFooThing().doOtherThing()
should be valid matchable, and replaced with
getCurrentBar().doBarThing()
or any other chain of method invocations.

Additional context
See Javadoc on ChainedMethodInvocationRefactor and associated tests for further example usage.

[monjurmorshed793]

A test case may be provided for understanding the issue more clearly.

[RadikalJin]

Good idea - added TestMethodInvocationRefactor.testInvocationChainedWithLargeMatchingAndReplacementChains.

[RadikalJin]

Fixed by @monjurmorshed793 under PR #85