[CHORE]: Upgrade rescript version from 10 to 11

[JeevaRamu0104]

Description:
In order to leverage the latest features, enhancements, and performance improvements provided by the Rescript language, we need to upgrade our current Rescript version. This upgrade will ensure that our codebase remains up-to-date and compatible with the latest ecosystem developments.

Objective:

Upgrade the Rescript version used in our project to the latest stable release.
Ensure compatibility with existing codebase and dependencies.
Test thoroughly to verify that all functionalities remain intact after the upgrade.
Address any compatibility issues or breaking changes introduced by the new version.
Tasks:

Version Assessment:

Research the latest stable version of Rescript and evaluate the benefits and changes introduced in this version.
Identify any potential compatibility issues or breaking changes that may affect our project.
Codebase Preparation:

Review the current codebase to identify any areas that may need modification or updates to accommodate the new Rescript version.
Make necessary adjustments to ensure compatibility and adherence to best practices.

Upgrade Implementation:

Update the project configuration and dependencies to use the new Rescript version.
Resolve any build errors or issues encountered during the upgrade process.
Test the upgraded codebase locally to ensure proper functioning.

Testing and Validation:

Conduct comprehensive testing to validate that all functionalities work as expected with the upgraded Rescript version.
Perform regression testing to identify and address any unintended side effects or regressions introduced by the upgrade.
Ensure compatibility with existing tests and test suites.

Documentation Update:

Update project documentation, including README files and version control system documentation, to reflect the upgraded Rescript version.
Provide instructions for developers on how to work with the new version and any changes they need to be aware of.

Acceptance Criteria:

The Rescript version in the project configuration is updated to the latest stable release.
All functionalities of the application work correctly after the upgrade.
Tests pass successfully, and there are no significant regressions compared to the previous version.
Project documentation is updated to reflect the changes introduced by the upgrade.

Additional Notes:

Coordinate with the development team to schedule the upgrade at a suitable time to minimize disruption.
Communicate the benefits and potential impact of the upgrade to stakeholders and ensure alignment with project goals.
Monitor the project closely after the upgrade to address any issues or concerns that may arise post-upgrade.