Expression 'evaluate' functions should not pass frameState paramter

[OmarShehata]

In the Cesium.StyleExpression page, the frameState description isn't very descriptive. Clicking on it to find out more goes to:

https://cesiumjs.org/Cesium/Build/Documentation/FrameState.html

Which is a 404.

[mramato]

FrameState is a private class, so it's not supposed to be documented or mentioned in the docs for that matter. So the problem here is in StyleExpression, not FrameState

[lilleyse]

Good catch @OmarShehata. FrameState is meant to be private so this is more a problem with Expression. Looking at it closer Expression doesn't actually use the frame state... maybe it once did but has since changed. Do you want to open a PR that removes the frameState parameter throughout Expression, ConditionsExpression, StyleExpression and anything that calls evaluate/evaluateColor?

[ggetz]

Fixed in #6890