Add mutex locks to data-sink-worker

[garrrikkotua]

Changes proposed ✍️

What

🤖 Generated by Copilot at 31e8fea

This pull request adds the functionality for locking and unlocking resources using the @crowd/redis library for the data sink worker service. It updates the configuration, dependencies, and logic for the service to use the Redis client and the mutex functions from the library. It also defines a custom TimeoutError class for handling timeout errors when acquiring or releasing locks.
​

🤖 Generated by Copilot at 31e8fea

Sing, O Muse, of the valiant data sink worker service
That connects to the swift-footed Redis client with skill
And locks and unlocks the activities and members with care
Using the cunning mutex logic of the @crowd/redis library

Why

How

🤖 Generated by Copilot at 31e8fea

• Add Redis configuration, client, and mutex logic to the data sink worker service (link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link, link)
• Update the package.json and package-lock.json files to add the @crowd/redis dependency and the name property for the other dependencies (link, link, link, link, link, link, link, link, link, link, link, link, link, link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.