fix: fix claiming for timelocked activity

[MarkNerdi996]

Summary

This PR fixes the calculation of the async status for activities. And with this fix, timelocked activities are again claimable

Changelog

- fix the calculation of async status for activities

Testing

Platforms

Please select any platforms where your changes have been tested.

• Desktop
  • MacOS
  • Linux
  • Windows
• Mobile
  • iOS
  • Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...

Checklist

Please tick the following boxes that are relevant to your changes.

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or modified tests that prove my changes work as intended
• I have verified that new and existing unit tests pass locally with my changes
• I have verified that my latest changes pass CI workflows for testing and linting
• I have made corresponding changes to the documentation

[nicole-obrien]

I have sent you some comments privately about cases that are not working as expected

[nicole-obrien]

We still have some issues with the states of the activity tiles.
When I am sending with a SDRUC only, it is showing the timelock icon from both sender and receiver perspective.
When sending witha timelock to an external address, it is showing the timelock on the senders activity when it is not needed.
When a timelock or expiration unlock expires we no longer need to show the icon.

[nicole-obrien]

LGTM!