IssueTracker

As part of aosp/2998197 we made a change to automatically chose the appropriate tv specific BringIntoViewSpec implementation on tv devices for our main components like LazyRow or HorizontalPager.

However, as was discussed in https://docs.google.com/document/d/1StJcbbIALEfyTddogznrMXmz3a21xUMhPYwWi08fXWI/edit and previous documents we still need to finalize what animation spec do we use on tv. Using tween() specs for bring into view animations is not entirely correct as specs with final duration can only be used when we know the final animation delta in advance, while the nature of bring into view mechanism is different: we scroll in the needed direction without knowing the final delta and are always ready to adapt to the new reported delta (for example when more items are composed by lazy layouts in between of the currently visible items and the requested target item). Because of that in the non tv implementation we were using `spring` based animation specs, which are better suited for animations with dynamic targets.

For those reasons, we are not even sure that the animation spec should be customizable at all, we will be promoting BringIntoViewSpec api in the next release and we would be in favour of removing this property from the api at all before doing so.

What I propose is we try to reevaluate the defaults we have. Try to understand why it was needed for you to update this animation spec and maybe our default is just incorrect, so we need to update it for both tv an non tv targets.