Create and Use InformationLeakTest.getRareResponses (#371)

[ic0ns]

Summary

• Moved getRareResponses method from SessionTicketPaddingOracleProbe to InformationLeakTest as a non-static method
• Updated all callers to use the new method location
• Added comprehensive unit tests for the method

Details

This PR addresses issue #371 by refactoring the getRareResponses method to make it reusable across different probes. The method identifies response patterns that occur rarely (at most N times) across all test vectors, which is useful for various padding oracle and timing attack analyses.

Changes made:

1. Moved method to InformationLeakTest: The method is now a proper instance method of InformationLeakTest, allowing it to access the test's vector containers directly
2. Fixed implementation: The method now correctly counts total occurrences across all vectors when determining rare responses
3. Updated callers: Both SessionTicketPaddingOracleProbe and TicketPaddingOracleResult now use the new method location
4. Added tests: Created comprehensive unit tests covering various scenarios including:
   • Empty response lists
   • Unique responses
   • Multiple rare responses
   • No rare responses
   • Integration with extended test data

Test plan

• Unit tests pass for the new getRareResponses method
• Existing tests still pass after refactoring
• Code compiles without warnings
• Spotless formatting applied