Add Example Showing Easings on Update Schedule instead of Startup

[CaptainLexington]

All of the existing examples show easings running in perpetuity (unless paused), initiating on startup. My use case is easing once between states that transition in response to changing conditions at runtime, and the vibrations I'm getting suggest my current method (running commands.entity().insert on every Update) is not the correct one.