Bring back useFrameCallback cleanup

[szydlovsky]

Summary

#6143 was supposed to improve cleanup of useFrameCallback but also deleted a needed line - setting callbackId of callback registry to -1. Seems like some code is dependent on this value and it caused some crashes such as this one: #6143. I haven't found a reliable way to reproduce the issue since we got the info from issue creator's sentry. Nonetheless, analysis of the code has shown that we need to set the callbackId to -1 on cleanup, otherwise we perform operations that shouldn't be done anymore (e.g there's this check:

react-native-reanimated/packages/react-native-reanimated/src/frameCallback/FrameCallbackRegistryUI.ts

Lines 105 to 107 in 818ed78

	if (callbackId === -1) {
	return;
	}

).

Test plan

As stated, the issue isn't really reproducible but the change doesn't risk any regression and time will tell if it fixes the problem