Make DutyCycleEncoder/DutyCycle constructors take a frequency parameter frequency

[rzblue]

We can't get the frequency from hardware anymore, so a specified frequency is a requirement to get a scaled duty cycle output.

The duty cycle HAL should expose the pulse width and everything else can be removed

[auscompgeek]

I think it'd be a good idea to add this as a constructor overload for 2026 as well, to give teams an easier path to migrate existing usage

[KangarooKoala]

Adding a constructor overload for 2026 would be nice, but it'd probably be annoying for the object to track whether or not it was constructed with a frequency and selectively throw in some method overloads. (TrapezoidProfile had a period where it did the same thing- See the TrapezoidProfile API refactor)

[rzblue]

it'd probably be annoying for the object to track whether or not it was constructed with a frequency and selectively throw in some method overloads.

DutyCycleEncoder already does this with setAssumedFrequency