feat: expose BufferedLinearInterpolator's less smoothed Update

[ToxPlayers]

Purpose of this PR

Exposed the more precise version of BufferedLinearInterpolator. The other update method is exposed but is more smoothed as explained in its existing doc. I've been using this more precise version and manually exposing it when the package is updated. I don't see a reason for it to be internal only.

Changelog

• Changed: BufferedLinearInterpolator.Update(float deltaTime, double tickLatencyAsTime, double minDeltaTime, double maxDeltaTime, bool lerp) scope from internal to public.

Documentation

• No documentation changes or additions were necessary.

Testing & QA (How your changes can be verified during release Playtest)

I've been using the function for my projects for a while and also tested it in this branch with no issues.

Functional Testing

Manual testing :

• Manual testing done

Automated tests:

• Covered by existing automated tests
• Covered by new automated tests

Does the change require QA team to:

• Review automated tests?
• Execute manual tests?
• Provide feedback about the PR?

If any boxes above are checked the QA team will be automatically added as a PR reviewer.

Up-port

Needed, should be exposed in 3.0.0 too

Backports

Not needed

[cla-assistant-unity]

All committers have signed the CLA.

[EmandM]

We have some pending changes for the BufferedLinearInterpolator in #4130. Will those changes help here? Or is this separate to what you're wanting?

[ToxPlayers]

This is different than #4130, it doesn't fix or change any functionality in the interpolation.
It only changes the scope of the lerp\smoothdamp Update method to public similar to the over smoothed double lerping Update method.
I can see the method is internal in #4130 too.

[NoelStephensUnity]

This is different than #4130, it doesn't fix or change any functionality in the interpolation. It only changes the scope of the lerp\smoothdamp Update method to public similar to the over smoothed double lerping Update method. I can see the method is internal in #4130 too.

We will look at exposing this method soon for v2.x.x.
Currently we are working on other features (#4123) that "changes the landscape" a bit.