support environments other than bevy_winit

[soqb]

when writing a tui with bevy, i found myself reaching for bevy_framepace but discovered it relies on bevy_winit in all cases.

this PR gates the refresh rate fetching logic behind a new "window" feature so that the plugin's main algorithm can be used outside of a windowed environment.

for Limiter::Auto, when the feature is not enabled, i chose 15fps as the default, which i think is reasonable for most tuis.

[aevyrie]

It seems strange to me to bake in defaults for TUI in a framepacing plugin. I'm not sure what the point of this crate is for that use case, it seems like you would be better off simply running a fixed rate or custom runner.

[stewartadam]

I would also find this useful to support outside of winit, for my use case I'm using Bevy and its ECS for a simulation that requires precise timing, but there's no graphical output. The entities maintain state in the ECS that is pushed out to hardware via serial or ethernet.