Only use item state when fetching icons

[maniac103]

sending icon requests, if available. Apparently this is wrong and we always need to use the item state for fetching icons, so roll back the respective code.

Fixes #3564

[maniac103]

@lolodomo Does this logic look correct to use (only use item state, never use widget state as formatted by state description), especially in the light of cases like mentioned in #3445 (item state = 0.45, widget state = 45 %)?

[mueller-ma]

Let's try it in beta.

[lolodomo]

@lolodomo Does this logic look correct

This is the current login adopted by all UIs Note that the icon servlet needs a deterministic value as current state. The widget pattern was imagined to control the format of the displayed value, but anything else, neither to control the persisted value nor the icon.
Changing and switching to the presented value for the icon, even if I can understand the logic, would probably introduced more difficulties than it solves, this issue seems to be a proof of this. Another example would be if you change your widget pattern, your dynamic icons n will no mir work.

Edit: and your example with 0.45 is just because the user forgot to set a unit to its item