Consider splitting the binding for scrolling vs. non-scrolling layouts.

[JakeWharton]

It is extremely rare that you change this property on a node at runtime. We waste a dummy node in the native tree to provide an indirection in case you do change it, however. But if we had two bindings, we could switch in a helper composable that implemented today's API allowing us to bypass this indirection.

Challenges:

• How do we do this in a backwards compatible way?
• Should we also do this for vertical vs. horizontal which would eliminate the intermediate node for scrolling?
• Do we need Support movableContentOf across protocol #1902 for this?