Resource bundles not linked when adding pod dependency to UnityFramework target

### Please fill in the following fields:
Unity editor version: 2019.3.3f
Play Services Resolver version: 1.2.136 (1.2.129+)
Features in Play Services Resolver in use (Android Resolver, iOS Resolver, VersionHandler, etc.): iOS Resolver
Plugins SDK in use (Firebase, Admob, Facebook, etc.): [AppLovin MAX Unity Plugin](https://github.com/AppLovin/AppLovin-MAX-Unity-Plugin)
Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac
Platform you are targeting (iOS, Android, and/or desktop): iOS
Scripting Runtime (Mono, and/or IL2CPP): Mono

### Please describe the issue here:
Starting from 2019.3+ Unity has added a new target (`UnityFramework`) to the exported project and JAR Resolver (starting 1.2.129, Related Issue: https://github.com/googlesamples/unity-jar-resolver/issues/282) always adds the dependencies to this target. This has an unintended side effect of the resource bundles not being linked to the main target. Cocoapods is correctly adding these bundles to the `UnityFramework` but they are not being linked to the main target.

Adding the pod dependency directly to the `Unity-iPhone` target fixes this issue, but currently there is no way to specify the target to which the framework needs to be added to JAR Resolver.

### Please answer the following, if applicable:
What's the issue repro rate? (eg 100%, 1/5 etc) 100%



It would be great if you could provide the ability to specify the desired target in the `Dependencies` file under the `iosPod` tag.