refactor(Worklets): remove supportsLocking parameter from Worklet Runtimes

[tjzel]

Summary

We already set it to true all the time.

Test plan

CI

[Copilot]

Pull Request Overview

This refactoring removes the supportsLocking parameter from WorkletRuntime constructors and related functions, as it was always set to true. The change simplifies the codebase by eliminating a redundant parameter and associated conditional logic.

• Removed supportsLocking parameter from WorkletRuntime constructor and related functions
• Eliminated conditional logic that checked the supportsLocking flag
• Cleaned up unused constants and assertions related to locking support

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
WorkletRuntime.h	Removed supportsLocking parameter from constructor and cleaned up member variables
WorkletRuntime.cpp	Simplified constructor and makeRuntime function by removing locking conditionals
RuntimeManager.h	Removed supportsLocking parameter from createWorkletRuntime method
RuntimeManager.cpp	Updated runtime creation calls to remove the hardcoded true parameter
JSIWorkletsModuleProxy.cpp	Removed supportsLocking parameter from createWorkletRuntime call

Comments suppressed due to low confidence (1)

packages/react-native-worklets/Common/cpp/worklets/WorkletRuntime/WorkletRuntime.cpp:53

• The removal of the null check for queue_ before calling push could cause a segmentation fault if queue_ is null. The lazy initialization logic was removed but queue_ is never initialized in the constructor.

};