Search API solr views could be not cached

I think this request is very tied to the Search API Solr module, which is the context in which it's required that the view not be cached. Applying this kind of differentiation might contradict the purpose of the insight and the warnings we issue in it. In other words, it's ultimately a heads-up that there may be something that needs to be reviewed.

I’ll leave the issue open in case anyone else thinks it's necessary to make this distinction, especially from a usability perspective.

There are many views generated by modules that are not cached because they are used to administer the site.

We are unable to exclude all of them by default since any module can create this type of view.

The best solution is to create a functionality that allows us to configure which views we want to exclude from the insights.

I change the title of the issue to implement this functionality.

Added dependency with issue 📌 Drop compatiblitiy with Drupal 9 version Active as some changes are not compatibles with drupal 9

Changes made

• Add the ability to alter the insight form.
• All insights are collapses
• Views can be excluded from the insights

@edu Great job! I just refactored the code that determines if an Insight is active or not to ensure compatibility with the form alterations.

Automatically closed - issue fixed for 2 weeks with no activity.