Clean Telemetry caches using a flush method

[freddyDOTCMS]

Parent Issue

No response

Problem Statement

Currently, we're employing a Cache within the Telemetry plugin to prevent running resource-intensive processes multiple times. For instance, querying the metric_temp table or retrieving data from the Elastic Search Index.

This Cache operates with an expiration time set at 10 minutes. However, this setup can lead to various issues. For instance, if in the future we adjust the frequency of the Telemetry Job to run every 5 minutes instead of the current interval, it could result in incorrect data retrieval because the Cache won't be cleared from the previous Job Execution. Similar issues could occur during testing.

Moreover, this fixed expiration time makes testing changes in the development environment cumbersome. Typically, we shorten the Job Execution interval for testing purposes, necessitating a corresponding adjustment to the cache expiration time in the code

Steps to Reproduce

• Change the Time to run the Telemetry job for each 5 minutos.
• Wait until the Job run the first time.
• Hit some Image API Called.
• Wait until the Job run again, you are going to get 0 for each API Image Metric.

Acceptance Criteria

• We need to flush the cache after the Job run instead of use an expire time.
• The bug describe on the "Steps to reproduce" section must not happend

dotCMS Version

latest Telemetry Plugin version

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response