fix: Make package.json accept newer versions of libs, e.g. Expo

[msluszniak]

Description

This PR fixes package.json in both expo and bare resource fetchers.

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

• Run minimal app that utilizes this version of our library with expo 55 (pack react native executorch and expo resource fetchers into tgz and install in template app) and check if everything works correctly.
• Run text to image example as this PR introduces changes in this package and check if everything works ok.

Screenshots

Related issues

Closes #882

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

[msluszniak]

Unfortunately, it seems that Expo 55.0.3 does not included fix with newer RNScreens version, which blocks us from bumping expo in our example apps look here: software-mansion/react-native-screens#3682. So we need to wait for this until this will be merged.

[chmjkb]

lgtm, but we need to do the same thing on the 0.7 release branch and release a patched version so 0.7 supports Expo 55

[chmjkb]

also TBH i don't understand why we're not just saving the image to FS on the native side, and returning the URI but that's not the point of this PR, am i missing something here?

[msluszniak]

also TBH i don't understand why we're not just saving the image to FS on the native side, and returning the URI but that's not the point of this PR, am i missing something here?

You mean specifically TextToImage TS part which was modified in this PR?
[EDIT] Same thing is with Style transfer. Fairly honest, I don't see any reason at first so I'll create an issue for that.

[chmjkb]

also TBH i don't understand why we're not just saving the image to FS on the native side, and returning the URI but that's not the point of this PR, am i missing something here?

You mean specifically TextToImage TS part which was modified in this PR? [EDIT] Same thing is with Style transfer. Fairly honest, I don't see any reason at first so I'll create an issue for that.

Yeah, style transfer does this:

std::string StyleTransfer::postprocess(const Tensor &tensor,
                                       cv::Size originalSize) {
  cv::Mat mat = image_processing::getMatrixFromTensor(modelImageSize, tensor);
  cv::resize(mat, mat, originalSize);

  return image_processing::saveToTempFile(mat);
}

It would make sense to me that TTI does this too (and we wouldnt have to do the png stuff). This isn't really related to changes made in this PR, but a thought of mine

[msluszniak]

Ok, right style transfer is ok, but typedocs are incorrect:

  /**
   * Executes the model's forward pass, where `imageSource` can be a fetchable resource or a Base64-encoded string.
   *
   * @param imageSource - The image source to be processed.
   * @returns The stylized image as a Base64-encoded string. THIS IS INCORRECT
   */
  async forward(imageSource: string): Promise<string> {
    if (this.nativeModule == null)
      throw new RnExecutorchError(
        RnExecutorchErrorCode.ModuleNotLoaded,
        'The model is currently not loaded. Please load the model before calling forward().'
      );
    return await this.nativeModule.generate(imageSource);
  }