allow icon configs to contain lists instead of strings, remove icons such as bat_N

[MaxVerevkin]

This is a breaking change but it will make adding "animated" icons a non-breaking change in the future.

[bim9262]

It seems like there's a few mismatches on the names in the icon files.

[ammgws]

On mobile

[ammgws]

So for some blocks like sound, the cut off points for each icon were nonlinear, do we want to try keep that behavior? From what I saw now what was previously 0..20 will be 0..33 if there are 3 icons in the list

[MaxVerevkin]

So for some blocks like sound, the cut off points for each icon were nonlinear, do we want to try keep that behavior? From what I saw now what was previously 0..20 will be 0..33 if there are 3 icons in the list

I'm okay either way. To restore previous behavior we can change [a,b,c] to [a,b,b,b,c].

[bim9262]

You might consider making this:

cpu = [ # fa-gauge-{min,max} are not free
    "\uf624", # fa-gauge
    "\uf624", # fa-gauge
    "\uf625", # fa-gauge-high
]

That way the gauge will go high at 66% which looks appropriate for the icon fa-gauge-high

[ammgws]

I'm okay either way. To restore previous behavior we can change [a,b,c] to [a,b,b,b,c].

This way allows the user more customisation but could be a bit confusing - guess it could be OK as long as we document it or add comment in the icon config file

[MaxVerevkin]

It took me seven months to realize that the current ^icon_ syntax does not support specifying an icon from that progression...