Rename Stepper builder methods

[luleyleo]

This fuses Stepper::min and Stepper::max to Stepper::with_range and renames Stepper::step as well as Stepper::wrap to Stepper::with_step and Stepper::with_wrap respectively.

Closes #684

[cmyr]

Looks good! with_wrap stands out as feeling a little weird, but 🤷‍♂

[xStrom]

Looks functionally equivalent.

[cmyr]

To bikeshed: how do we feel about with_wrapping or with_wraparound?

[luleyleo]

with_wraparound seems good to me, should I change it to that or wait a little longer?

[xStrom]

You can just change it to with_wraparound now.

Not related to your work per se, but I was looking at this Stepper code and the wraparound doesn't even work. With wraparound set the Stepper can only have its value as the min or max.

Looking at the PR (#308) it seems that initially the code was maybe more functional.

if (*data - old_data).abs() > EPSILON {
    // callback
    (self.value_changed)(ctx, data, env);
} else if self.wrap {

However in a commit titled Adress stepper review feedback that was removed and changed to the current non-working code. Also that change doesn't seem to be based on any actual reviewer feedback, so I guess some sort of mistake.

Feel free to fix the wraparound code here, or if you'd rather not that's fine too and we'll just merge the method renames only.

[luleyleo]

For now I've just renamed with_wrap to with_wraparound

The functionality in itself is indeed completely broken, I think I will deal with that in a separate PR after I'm done with #632

[cmyr]

Thanks, this looks good! I'm going to make a few little doc fixes but happy to merge.