✨ Improve Animator copying (createAnimatorWithAnimationsFrom) by avoiding our patch

[mrousavy]

We currently have a patch that allows the user to use animations from a different entity.

react-native-filament/package/cpp/core/FilamentAssetWrapper.cpp

Lines 44 to 53 in 4c37b70

	std::shared_ptr<AnimatorWrapper> FilamentAssetWrapper::createAnimatorWithAnimationsFrom(std::shared_ptr<FilamentAssetWrapper> otherAsset) {
	#ifdef HAS_FILAMENT_ANIMATOR_PATCH
	// TODO(copy-animations): We currently copy animations from an asset onto another instance (different model than the original asset), we
	// should replace this with once we found a good solution discussed here: https://github.com/google/filament/issues/7622
	Animator* animator = new gltfio::Animator(otherAsset->_asset.get(), _asset->getInstance());
	return std::make_shared<AnimatorWrapper>(_asset, animator);
	#else
	return getAnimator();
	#endif
	}

For example, Entity A has 30 animations, Entity B has 0 animations, with our patch (``) you can use all of Entity A's 30 animations on Entity B.

The implementation of the patch is a bit rough as we just create a new Animator* pointer - which seems to work fine even in production, but we wanted to avoid the use of a patch in Filament for multiple reasons:

• Avoiding a patch by having an upstream change is just always better
• We are abusing the API a bit here, it wasn't really built like this
• We cannot use Filament from CocoaPods/Maven now, so we have to build it manually and ship it over npm to use our patch

We already created an issue in google/filament and are hoping to find a solution that can be merged upstream there: google/filament#7622

[hannojg]

A part from the patch can already be removed as this PR has been merged in filament.
Will put out a update PR once I find the time!

• fix: apply applyCrossFade to correct entity google/filament#7665

[hannojg]

We are currently waiting for this PR to be approved:

• feat: updateBoneMatricesForInstance google/filament#7859