DutyCycleEncoder rewrite is not documented as "Breaking"

[chauser]

Describe the bug
DutyCycleEncoder.getAbsolutePosition changed toDutyCycleEncoder.get but https://docs.wpilib.org/en/latest/docs/yearly-overview/yearly-changelog.html#new-for-2025 just says DutyCycleEncoder was rewritten. DutyCycleEncoderSim is also affected for both the get and set methods.

There may be a similar issue with AbsoluteEncoder (mentioned as rewritten on the same line of the change log).

Expected behavior
At a minimum, the change log should flag the breaking change. Maybe the project importer could make the change automatically? Is that safe? I.e., is the change as simple as changing the method name or are there other semantic considerations that need to be accounted for? If so, some guidance is needed.

[ThadHouse]

The behavior changed enough where we'd probably rather have the break so users actually look at where they used that code. Rollover support was completely removed, as it was broken in hardware. Doing this let us add better mapping support, so getting the absolute value as expected should be easier.

[KangarooKoala]

Should we update the docs page to describe it as breaking, though? (And maybe move it closer to the top? I'm not familiar with the typical structure of the "New for ..." pages to know if there's already a particular order they're in)

[chauser]

OK, that seems reasonable. I think then there needs to be a description of what to look at in user code that might be broken. The documentation for get is : "Get the encoder value since the last reset. This is reported in rotations since the last reset." which seems incorrect -- there isn't a reset method, so what would that mean? And "rotations" suggests to me that rollover support might be present. I think the new behavior is "return the encoder position in the interval 0..1 rotation".