[IJ Plugin] Cache GraphQL project config

[BoD]

In order to contribute the location of schemas/operations to the GraphQL plugin (the GraphQL project config), the Apollo plugin needs to fetch the Gradle tooling models from all Apollo modules of a project.

This can't be done all at once unfortunately, so is implemented by iterating over all modules and executing Gradle on each. On big projects, when there's a lot of modules, and/or on slow machines, this can take a long time (e.g. >10 minutes), and while this is ongoing, the GraphQL plugin will provide a degraded experience (missing references while editing files, etc.).

This information could be stored in the project, so when it is re-opened, it can be contributed right away.

In most project, we can expect that the project's structure doesn't change often, so this should provide a nice experience in most cases. Worst case, the cached configuration provided is out of date, and the GraphQL plugin will provide a degraded experience while the tooling models are being fetched - which is already the case in the current situation.

[BoD]

Also, could there be a way to implement a dedicated Gradle task that can provide all this information in just 1 run?

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Kotlin usage and allow us to serve you better.