fix: added support for bindings in invokeAPI

[sagardspeed2]

Describe your changes

Added support for bindings in invokeAPI

Screenshots [Optional]

Issue ticket number and link

Closes #848

Checklist before requesting a review

• I have performed a self-review of my code
• I have added tests
• I have added a changeset pnpm changeset add
• I have added example usage in the kitchen sink app

[changeset-bot]

🦋 Changeset detected

Latest commit: 904fc3c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@ensembleui/react-framework	Patch
@ensembleui/react-runtime	Patch
@ensembleui/react-kitchen-sink	Patch
@ensembleui/react-preview	Patch
@ensembleui/react-starter	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Visit the preview URL for this PR (updated for commit 904fc3c):

https://react-kitchen-sink-dev--pr1024-848-use-bindings-in-q97gh7s9.web.app

_{(expires Wed, 12 Feb 2025 14:44:43 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 6267897ade2ba783b6db70a53a60fc3946d625e9}

[evshi]

How does this work with the useInvokeAPI hook? That hook clearly checks if the API name exists before invoking.

[sagardspeed2]

if you check useEnsembleAction, in useInvokeAPI we are using useRegisterBindings for evaluate API name and then we check that is API name exists in screenContext before invoking the api, and here when user trigger the api through ensemble.invokeAPI, we are using evaluateDeep to evaluate the api name and then we are checking that name with screenContext and if we found the api, only then we invoke it