Clean up plugin build process #8348
Description
While reading about plugin structure as part of decisions around dart plugin, we decided to reorganize the flutter plugin as well (mostly from @jwren). The goal is to make plugin building easier to understand and easier to debug by following conventions of IntelliJ plugin setup and gradle and removing complex paths that were added for historical reasons but are no longer needed.
- remove build files in flutter-idea and flutter-studio subdirectories - instead of using a module structure for intellij vs Android studio plugins, we should be able to specify code to include/exclude in plugin.xml files Consolidate gradle build files #8278
- flatten directories to remove flutter-idea and flutter-studio Move contents of flutter-idea and flutter-studio to top level #8343
- Remove required Android studio plugin dependency ⚙️ Flip
org.jetbrains.androidto optional #7949 - Consider how to support multiple platform versions - this could mean generating a single plugin that spans versions, using branches, or keeping the status quo (product-matrix.json). The complex build process for multiple versions was more necessary when platform APIs were changing quickly, but may not be needed now.
- Reduce dependency on plugin.dart and related files - we are doing a lot of customized file reading and writing and other tasks that could likely be replaced with gradle and IntelliJ platform configuration. (Use gradle build file to populate changelog #8360, Remove xml templates #8363)
- Use more conventional directory structure?