fix(lexicon): send single notice/warning when using unknown config key

[ArtificialOwl]

Right now, if an app set the Lexicon Strictness to NOTICE or WARNING, 9 duplicate logs entries are generated when using

 ./occ config:app:set my_app abcd --value '123'

{
  "reqId": "Hdt7ARDAZhnhBLXiuhKj",
  "level": 1,
  "time": "2025-08-29T12:38:09+00:00",
  "remoteAddr": "",
  "user": "--",
  "app": "no app in context",
  "method": "",
  "url": "--",
  "message": "The app config key my_app/abcd is not defined in the config lexicon",
  "userAgent": "--",
  "version": "32.0.0.6",
  "data": []
}

Reason for that is that the key is used multiple time in the process.
The fix is to only print once and filters all similar reports

[provokateurin]

Can you use some other key than the literal log message? 🙈

[ArtificialOwl]

I had the same thought; the solution i had in mind was to send at least the key, or the app+key string, to the method and use it as index. adding some complexity to the code. And doing a checksum was overkill.

My own conclusion was that, at the same time, the code is deep into the loop and should not be executed that much.

But yes, I can; should I ?

[ArtificialOwl]

• added limit also to IUserConfig
• only use appid+key as index of array strictnessApplied[]

[AndyScherzinger]

🐘