[RNE Rewrite] feat: add input validation and JSI conversion utilities

[barhanc]

Description

Refactors the C++ layer by pulling two families of scattered, copy-pasted utilities out of individual translation units and into purpose-built, reusable modules:

• cpp/core/conversions.{h,cpp} JSI -> C++ type coercions
• cpp/core/tensor_helpers.{h,cpp}: tensor acquisition, locking, and shape/dtype validation

Motivation

The old code had two recurring problems that became impossible to ignore as the extension surface grew:

JSI coercion was inlined everywhere

Every file that needed to read a number, string, or array out of a jsi::Value had its own copy of the same defensive checks, cast chains, and error-message construction. A bug or policy change (e.g. how null is treated, or which format an error message takes) had to be hunted down and patched in every translation unit independently.

Tensor validation was duplicated across all extension operations

Every operation in box_ops, image_ops, operations, and tokenizer that accepted a Tensor argument re-implemented the same sequence: unwrap the jsi::Value, cast to TensorHostObject, acquire the appropriate
shared/exclusive lock, and assert dtype + shape constraints. This led to subtle inconsistencies in error messages and locking strategies between operations.

Introduces a breaking change?

• Yes
• No

Type of change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update (improves or adds clarity to existing documentation)
• Other (chores, tests, code style improvements etc.)

Tested on

• iOS
• Android

Testing instructions

• Build all example apps on both Android and iOS and test that nothing is broken.

Screenshots

Related issues

Closes #1270
Closes #1268

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings

Additional notes

Since this PR changes quite a lot of stuff in core/ it can also be used for #1268

[barhanc]

@msluszniak This is still a draft and there are still quite some rough edges to polish, but could you take a look if this approach is something you would agree on and if there are any other aspects I missed. I was thinking that we could also use this PR for #1268 since adding the validation/conversion helpers modifies quite a lot of core code so it would be good to review and streamline also the other aspects.

[msluszniak]

I like this concept. I combines elegance of short macros with flexibility of manual code. Just very small nits, will dive into it later today / tomorrow. I like usage of std::format, we previously tried use it in old codebase, but because it required some version of iOS we eventually dropped it, but I don't think it will be a case now.

[msluszniak]

Another batch of comments.

[barhanc]

The core/ changes are ready for the next pass. Later I will also polish the code in extensions/.

[msluszniak]

Two more comments

[msluszniak]

No more comments from my side, I'm checking demo apps on physical android and ios simulator.

[msluszniak]

One comment not related to the changes but spotted in demo app testing, can we fix the overlapping android nav bar with buttons in classifications section?

[msluszniak]

Maybe a bit loose requirement on minimal confidence since 28% was accepted, do you remember what is the actual thershold?

[msluszniak]

Two small comments which where strictly demo app related, so they might be addressed in a separate PR. 🚀

[barhanc]

Maybe a bit loose requirement on minimal confidence since 28% was accepted, do you remember what is the actual thershold?

It is specified in the models.ts (advantage of the new implementation -- all model specific properties live in one file), assuming this is YOLO it's set to 0.25 --- definietly too low.