Fix: Double-counting time after hat reactivation in HatsTimeFrameModule

[tanapl]

Test Case Breakdown:

1. Initial Period:

• The user wears the hat for 100 seconds.
• The getWearingElapsedTime function should return 100n after time.increase(100).

2. Deactivate:

• After deactivation, the time should pause, and no additional time should be counted.
• Increasing time by 50 seconds while deactivated should not affect the elapsed time (getWearingElapsedTime should still return 100n).

3. Reactivate:

• After reactivating the hat, time should continue counting from 100n, not resetting or counting the deactivated period.
• After adding 100 seconds post-reactivation, the total elapsed time should now be 200n (100n from before deactivation and 100n after reactivation).

[tanapl]

Problem (Fixed)

• Test Failures:
  The test suite for HatsTimeFrameModule was failing due to discrepancies between the expected and actual elapsed times calculated by the contract.

• Time Calculation Errors:
  The getWearingElapsedTime function in the contract was incorrectly calculating the elapsed time, particularly during periods when the hat was inactive.

• Inconsistent block.timestamp:

• The tests did not account for how block.timestamp increments during transactions in the test environment, leading to off-by-one errors.

Result

• Passing Tests:
  All tests now pass, confirming that the HatsTimeFrameModule functions as intended.

• Accurate Time Tracking:
  The contract correctly calculates the elapsed time a wearer has actively worn a hat, properly accounting for activation and deactivation periods.

• Robust Testing:
  The improved test suite provides reliable verification of contract behavior, reducing the likelihood of future discrepancies.