a few optimizations for dashboards

[orthagh]

Description

• SELECT COUNT without JOIN doesn't need to be DISTINCT
• GROUP BY id instead name/completename on "multiple" graphs make a significative gain
• add a composite index (is_deleted, is_template) to filter out unactive item (this has a significative gain on softwares)

  This has been extended to all other itemtype with this key combination
  regex:

  /CREATE TABLE `([a-zA-Z_]+s)`\X[^;]*`is_deleted`\X[^;]*`is_template`/gmUs
  

• tempory cache for Filter::getAppliableFilters where most of the hit was

[trasher]

You will have to remove the is_template and is_deleted keys to fix tests.

I do not know if you plan other improvements, but those ones shoudl target next release I guess.

[orthagh]

You will have to remove the is_template and is_deleted keys to fix tests.

Probably only is_deleted as it's the first is the construction of the composite key, is_template is still required/

[orthagh]

TODO: cache management for filters isn't clearable at the moment, and I need to find another way to store/delete.
This is a priority because it takes 100ms on each card/widget to check if there are appliable filters even when no filters exist. As we use AJAX to display cards, it delays every other card, and this cumulates very fast.
On my local instance, neutralizing this piece of code is a raw 1.5s~ gain. I suppose this could have greater impact on cloud/online instances.

Edit: done by a short ttl

[AdrienClairembault]

There are PHPStan errors