Extract Mutation Strategy from RankInvariantChecker and Update Tests

[BashithaShamila]

In this pull request, I have refactored the RankInvariantChecker class by extracting the mutation strategy into a separate MutationStrategy interface. This enhancement promotes greater modularity and flexibility, allowing developers to easily implement and integrate custom mutation strategies without modifying the core RankInvariantChecker logic. Additionally, I introduced a default mutation strategy implementation and updated the relevant tests to ensure seamless functionality with the new structure. These changes improve the maintainability and extensibility of the codebase, facilitating future enhancements and adaptations.

[leliel12]

• The tests and the API documentation of the new strategies are needed
• In other hand maybe the strategy can be implemented as a function (like all the strategy patterns in python). a New class is unnecessary

I imagine something like:

def my_mutation(**kwargs):  # we must decide with "kwargs" are necesary
   ....
   
rrt1 = RankInvariantChecker(mutation_strategy=my_mutation)

My suggestions are to reduce the number of new modules, reduce the number of new documentation and obviously reduce the number of testing. Making this code more maintainable