Allow the use of native ios and android framework's solutions/projects rather than an pre-build .framework/.aar file

Is your feature request related to a problem? Please describe.
At the moment as a plugin developer I have to pre-build my native framework I have from iOS into an embedded .framework file and for Android into an .aar file and place those into the platforms directory of my plugin. I would like to be able to tell the NativeScript CLI where the actual Xcode/Android Studio projects if my plugin are located and have the CLI use them as "referenced projects" for the output that it created in the platforms folder of the {N} application. The idea is to be able to open that output into Xcode/Android Studio and if that output from the CLI is using a referenced of my native framework's solutions they will be included as "side" projects and I will be able to change my native code and use the IDE rebuild and start functionality (like a native iOS and Android development workflow)

Describe the solution you'd like
Currently the CLI creates the output in the the "platforms" directory (after tns build ios/android command) in such a way that it simply uses the pre-build .framework/.aar files from each node_modules {N} plugin into the build Xcode/Android Studio project of the {N} app. If the CLI can instruct the runtime to not simply use and look for .framework/.aar files but instead use an actual Xcode/Android Studio solution which builds those .framework/.aar files it will be possible to implement an functionality into the iOS and Android runtimes that will use those projects.

Describe alternatives you've considered
Currently the only way to streamline the development workflow of a plugin developer who creates a native iOS/Android library is to either:

1. Build and manually move the product of the library to the "platforms" directory of his plugin
   or
2. Use the newly created "nativescript-dev-debugging" plugin which provides workflows for such actions

The drawbacks from both approaches is that they require a full build if the {N} app after the library is replaced (--syncAllFiles).

Commencez par suivre la manière dont tns build ios/android crée la sortie de l’application dans le répertoire platforms et utilise actuellement les fichiers .framework et .aar des plugins. Comparez ce workflow avec nativescript-dev-debugging ; le travail est considéré comme terminé lorsque les projets Xcode et Android Studio fournis par les plugins peuvent être référencés, inclus comme projets secondaires et reconstruits via le workflow de l’IDE natif.