fix: add usage stats for dynamic menu entries

[tltv]

Fixes: #20209

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Test Results

1 141 files  ± 0  1 141 suites  ±0   1h 26m 14s ⏱️ + 1m 4s
7 447 tests ± 0  7 397 ✅ ± 0  50 💤 ±0  0 ❌ ±0 
7 808 runs  +24  7 748 ✅ +24  60 💤 ±0  0 ❌ ±0 

Results for commit f05575f. ± Comparison against base commit 2d42aad.

[mcollovati]

The other PR related to statistics sets entry name in Constants class, and it also has a has-xxxx format.
Is it a convention to have flow/xxx instead of has-xxxx for Flow stats?

[tltv]

The other PR related to statistics sets entry name in Constants class, and it also has a has-xxxx format. Is it a convention to have flow/xxx instead of has-xxxx for Flow stats?

No, I created this first without any guidelines with naming. Other PR has already existing naming pattern to follow. However, we have other similar patterns with flow/ in Constants. Point is to be clear it's Flow feature. I considered first to use flow/MenuConfiguration, but as this should mark menu entry usage only, not whole class, then flow/dynamic-menu-entries feels better.

[mcollovati]

LGTM.
I wonder if we should in the future do a little refactor and group all statistic constants in a dedicated class.