…-0.64.0

Upgrade to gradle 7.1.1

Add tarball

Routine RN package upgrade.

…tive-0.66

Update to RN 0.66.2

Update CI branch from master to trunk

# Conflicts:
#	android/build.gradle
#	package.json

The original configuration tries to fetch the RN version of the app and find a matching AAR. In our case, since we control the RN version, we can simplify the configuration by providing a single and specific RN version.

Update `trunk` with upstream version `2.2.4`

Update wp-fork to version `2.2.4`

# Conflicts:
#	.github/workflows/main.yml
#	Common/cpp/Tools/JSIStoreValueUser.cpp
#	Common/cpp/headers/Tools/JSIStoreValueUser.h
#	Example/android/app/src/main/java/com/swmansion/reanimated/example/MainApplication.java
#	Example/android/build.gradle
#	Example/android/gradle.properties
#	Example/android/gradle/wrapper/gradle-wrapper.properties
#	Example/android/settings.gradle
#	Example/ios/Podfile.lock
#	Example/package.json
#	Example/yarn.lock
#	RNReanimated.podspec
#	android-npm/build.gradle
#	android/build.gradle
#	android/gradle/wrapper/gradle-wrapper.jar
#	android/gradle/wrapper/gradle-wrapper.properties
#	android/gradlew
#	android/gradlew.bat
#	createNPMPackage.sh
#	ios/native/NativeProxy.mm
#	ios/native/REAInitializer.h
#	ios/native/REAInitializer.mm
#	ios/native/UIResponder+Reanimated.mm
#	package.json
#	src/reanimated2/js-reanimated/index.web.ts
#	yarn.lock

## Description
This PR adds a getter for `ReactInstanceManager`. The motivation for this PR is to fix issues software-mansion#2719 and software-mansion#2801

Those Android apps whose application class does not implement `ReactApplication` or simply have a different mechanism for storing a `ReactInstanceManager`, currently they have an incompatibility with `react-native-reanimated` ending in a crash when launching the app, as the issues indicates.
Normally, those apps are where [React Native is integrated with existing Android apps](https://reactnative.dev/docs/integration-with-existing-apps)

So, introducing this getter allows us to override this getter and implement a custom way to return the `ReactInstanceManager` to be used by `react-native-reanimated`.

<!--
Description and motivation for this PR.

Inlude Fixes #<number> if this is fixing some issue.

Fixes # .
-->

## Changes
- Added `getReactInstanceManager` method for android.
<!--
Please describe things you've changed here, make a **high level** overview, if change is simple you can omit this section.

For example:

- Added `foo` method which add bouncing animation
- Updated `about.md` docs
- Added caching in CI builds

-->

<!--

## Screenshots / GIFs

Here you can add screenshots / GIFs documenting your change.

You can add before / after section if you're changing some behavior.

### Before

### After

-->

## Test code and steps to reproduce
This is an example of how to use and override this getter. It is necessary to manually link `react-native-reanimated` before to be able to do it.
```java

public class MainActivity extends Activity implements DefaultHardwareBackBtnHandler {

    private static ReactInstanceManager mReactInstanceManager;
    ...

    @OverRide
    protected void onCreate(Bundle savedInstanceState) {
       ...
        List<ReactPackage> packages = new PackageList(getApplication()).getPackages();

        // Adding manually Reanimated package here, with overriding getReactInstanceManager method
         packages.add(new ReanimatedPackage() {
            @OverRide
            public ReactInstanceManager getReactInstanceManager(ReactApplicationContext reactContext) {
               // Implement here your way to get the ReactInstanceManager
               return MainActivity.getReactInstanceManager();
            }
         });

        mReactInstanceManager = ReactInstanceManager.builder()
                .setApplication(getApplication())
                .setCurrentActivity(this)
                .setBundleAssetName("index.android.bundle")
                .setJSMainModulePath("index")
                .setJSIModulesPackage(new ReanimatedJSIModulePackage()) // Adding ReanimatedJSIModulePackage here
                .addPackages(packages)
                .setUseDeveloperSupport(BuildConfig.DEBUG)
                .setInitialLifecycleState(LifecycleState.RESUMED)
                .build();
       
        ...
    }
...
}
```
<!--
Please include code that can be used to test this change and short description how this example should work.
This snippet should be as minimal as possible and ready to be pasted into editor (don't exclude exports or remove "not important" parts of reproduction example)
-->

## Checklist

- [x] Included code example that can be used to test this change
- [ ] Updated TS types
- [ ] Added TS types tests
- [ ] Added unit / integration tests
- [ ] Updated documentation
- [ ] Ensured that CI passes

Update `wp-fork` to version `2.4.1`

# Conflicts:
#	.github/workflows/main.yml
#	Common/cpp/Tools/JSIStoreValueUser.cpp
#	Common/cpp/headers/Tools/JSIStoreValueUser.h
#	Example/android/app/src/main/java/com/swmansion/reanimated/example/MainApplication.java
#	Example/android/build.gradle
#	Example/android/gradle.properties
#	Example/android/gradle/wrapper/gradle-wrapper.properties
#	Example/android/settings.gradle
#	Example/ios/Podfile.lock
#	Example/package.json
#	Example/yarn.lock
#	RNReanimated.podspec
#	android-npm/build.gradle
#	android/build.gradle
#	createNPMPackage.sh
#	ios/native/NativeProxy.mm
#	ios/native/REAInitializer.h
#	ios/native/REAInitializer.mm
#	ios/native/UIResponder+Reanimated.mm
#	package.json
#	src/reanimated2/js-reanimated/index.web.ts
#	yarn.lock

Update `trunk` with upstream version `2.4.1`

# Conflicts:
#	RNReanimated.podspec
#	android-npm/build.gradle
#	android/build.gradle
#	createNPMPackage.sh
#	package.json
#	yarn.lock

…re-mansion#3162)

## Description
ReactApplicationContext.getCurentContext sometimes return null. This causes a crash (NullPointerException) in reanimated due to not checking if context exists. As per react native's examples, we can only measure device metrics when current activity is not null (https://github.com/facebook/react-native/blob/8bd3edec88148d0ab1f225d2119435681fbbba33/ReactCommon/react/nativemodule/samples/platform/android/SampleTurboModule.java#L56)

Fixes software-mansion#2959.

## Changes

Check if current activity is not null before measuring the device.

…mation-crash

Fix crash related to Android layout reanimation due to `NullPointerException`

…odes manager

Pausing the display link on invalidation will still make it call the onAnimationFrame selector one more time as its already schedule. When this happens animation blocks will be called and crash while accessing the jsi runtime thats already dealloced.

…-link

Invalidate display link instead of pausing it when invalidating the nodes manager

# Conflicts:
#	RNReanimated.podspec
#	android-npm/build.gradle
#	android/build.gradle
#	android/gradle.properties
#	createNPMPackage.sh
#	package.json
#	yarn.lock

Update wp-fork to version `2.9.1`

Update `trunk` with upstream version `2.9.1`

…ball

Update tarball for `2.9.1`

Upgrade compile and target sdk version to Android API 31

# Conflicts:
#	android-npm/expo/linking.gradle
#	android/build.gradle
#	package.json
#	react-native-reanimated-2.4.1-wp-4.tgz

…nneeded code comparing the changes from the original repo's file in 2.9.1.

Updates createNPMPackage.sh to fix an issue after merge

Upgrade compile and target sdk version to Android API 31 (version 2.9.1)

…n#3559)

Reanimated is not fully compatible with Jest 28+ even after the PR software-mansion#3347. Using it with Jest 28+ leads to this error:

<img width="796" alt="Ekran Resmi 2022-09-10 15 00 33" src="https://user-images.githubusercontent.com/22980987/189482337-cc2655f6-9463-4a05-9998-5fc3592f5cc0.png">

The reason is, the "expect" module's export approach has changed starting from Jest 28. It used to export the `expect` function directly, as can be seen [here](https://github.com/facebook/jest/blob/v27.5.1/packages/expect/src/index.ts#L441).

This means, requiring the "expect" module like this

```ts
const expect = require('expect')
```

was providing direct access to the `expect` function alongside with its attached methods, like `extend`.

This has [changed with Jest 28](https://github.com/facebook/jest/blob/v28.0.0/packages/expect/src/index.ts#L449). `export default expect` is the new export statement, which means requiring the "expect" package returns the module object, instead of the function.

software-mansion#3347 PR attempts to fix this error by assuming "expect" package should throw an error with Jest 28 and it can catch that and require the "expect" from the `@jest/globals` package for Jest 28+ project but it's not the case in reality. "expect" package is still shipped with Jest 28, so, requiring it doesn't throw an error as expected in the PR.

By knowing the export difference, I checked if the value of the module is object or not after requiring it. If it's an object, it means user is on Jest 28+ codebase. The rest is the same with the previous PR. I require the "expect" function from `@jest/globals` and use it.

Tested on Jest 29 and Jest 27.5.1

Fixes software-mansion#3553 and software-mansion#3215.