fix: strengthen error handling and test coverage for Connect component

[Krishprajapati15]

Overview

This pull request strengthens the robustness and reliability of the Connect component and its test suite. It addresses two key issues:

1. Error Handling for Braintree SDK Availability
   The code now explicitly checks for the presence of window.braintree and window.braintree.connect before attempting to use them. If either is missing, a clear error is thrown and logged, preventing ambiguous runtime failures and making debugging easier.
   Why needed: In asynchronous, script-loaded environments, the Braintree SDK may not always be loaded as expected. Without this check, attempts to use undefined objects would result in hard-to-debug errors.

2. Preservation of Error Stack Traces
   The error handling was improved to rethrow the original error object instead of wrapping it in a new Error. This preserves the stack trace and original message for better troubleshooting.
   Why needed: Wrapping an error can obscure the original context, making error logs less useful for pinpointing issues in production.

3. Test Suite Improvements

   • Added a unit test to verify that an explicit error is thrown when window.braintree or window.braintree.connect is missing.
   • All previous test logic and coverage are preserved.
     Why needed: Ensures new error handling logic is covered and prevents regressions.

Summary of Changes

• Added explicit runtime check and error for missing window.braintree or window.braintree.connect in getConnectComponent.
• Changed error handling to rethrow original error objects, preserving stack trace and context.
• Added a unit test in the test suite to validate error throwing when Braintree SDK is not present.
• Preserved all existing code comments and unchanged logic.
• No changes made to code files that did not require fixes.

Motivation

These changes were introduced to address real-world scenarios where the Braintree SDK might not be loaded due to network, configuration, or script loading issues, which previously led to silent or confusing failures. Additionally, improved error propagation ensures that logs and monitoring tools provide actionable information for developers and support teams.

Testing

• All previous and new tests pass.
• The new test case for missing Braintree SDK is included and verified.
• No regression in Connect or Fastlane memoized exports.

Impact

• More robust and reliable initialization of Connect component.
• Easier debugging and support in production due to clear error messages and preserved stack traces.
• Improved test coverage for edge cases.

---

If you have any questions or need further clarifications, please let me know in the comments.

[github-actions]

This pull request has been automatically marked as stale. If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated.