fix(android): build issues where dependent libraries can't link RNWC

[hannojg]

Basically addresses all bugs such as:

• Android: Cache issue when rebuilding, need to clear cache to fix mrousavy/nitro#674
• Android: Cache issue when rebuilding, need to clear cache to fix mrousavy/nitro#674
• Vision-camera and worklets-core 1.5.0 build issues - undefined symbol: RNWorklet #235
• Worklets-core not working with react-native 0.78 #242
• 🔧 Build Error mrousavy/react-native-vision-camera#3425
• 🔧 Execution failed for task ':react-native-vision-camera:buildCMakeDebug[arm64-v8a] mrousavy/react-native-vision-camera#3551

Details:

There is a bug with the gradle android plugin that causes libraries that depend on the prefab we publish to not be able to find the native libraries.

There are two problems to why this bug occurs:

1. The prefabConfigurePackage task might run before we build our native libaries. This will cause AGP to treat our library as a "header only" library, in that case it generates a CMake file, which doesn't include the native library and thus linking fails.
   • Special note: the AGP always creates a header publication file when we run configureCMake,there is no way to avoid that.
2. There are cases where AGP for a dependent library already ran the prefab CLI when for this library we only had the header publication.
   Even when the publication in our library changes (because native libs were build) the dependent library wouldn't pick up on that change, as the only place where the AGP would re-run the prefab CLI (which generates the cmake file) is here.
   However, no changes are detected, although our prefab publication changed. Thus we manually touch a file to mark it as changed, and that will trigger the CLI to run

Notes:

• This fix needs to be cherry-picked to v2 of RNWC as well (not sure though how many people use it)
• Other libraries that use prefab mechanisms such as nitro-modules have to implement this as well