fix: reanimated 3.0 compatibility

[kirillzyusko]

📜 Description

Fixed package compatibility for reanimated version lower than 3.7.0

💡 Motivation and Context

On Reanimated 3.7.0- the useEvent handler returns ref (with current property). After reanimated 3.8.0 it returns an object that contains workletEventHandler. Somehow in #1209 I thought that it returns the event handler directly (not in ref). So I declared the object as object-or-direct-handler.

In #1585 (comment) I realized that I made a mistake, so in this PR I eliminated a dead code and fixed compatibility.

Follow up for #1209 (something that had to be implemented there from the beginning).

Closes #1585 (comment)

📢 Changelog

JS

• rename WorkletHandlerOrWorkletHandlerObject to WorkletHandlerContainer;
• replace currentHandler.* with currentHandler.current.*;
• updated titles of unit tests;

🤔 How Has This Been Tested?

Tested via this PR (e2e tests).

📸 Screenshots (if appropriate):

📝 Checklist

• CI successfully passed
• I added new mocks and corresponding unit-tests if library API was changed

[kirillzyusko]

Hey @ahulterstrom 👋

Could you please confirm that these changes fix a problem 2 described in #1585 (comment)? 🙏

[github-actions]

📊 Package size report

Current size	Target Size	Difference
334397 bytes	334380 bytes	17 bytes 📈

[github-actions]

1. Runtime error when passing direct WorkletHandler
   Why: The code incorrectly assumes all handlers are either wrapped with 'current' or 'workletEventHandler'. Passing a direct WorkletHandler leads to accessing undefined properties, causing crashes.
   Fix: Ensure the code handles both wrapped and unwrapped handler types correctly.

2. Type mismatches in handler processing
   Why: Changes to WorkletHandlerContainer type may cause TypeScript to misinterpret handler structures, leading to incorrect method calls and potential runtime errors.
   Fix: Review and adjust type definitions to properly accommodate all valid handler formats.

LGTM