Detect recursive structures in data binding

This CL fixes two bugs in data binding both related to recursive
data structures.

If you provide data binding a class that looks like Foo<T : Foo> or
Foo : LiveData<T :  Foo>, it would go into a stackoverflow or OOM
trying to parse it since it would land back into the same class
as it tries to resolve values.

This CL fixes it by adding a tracker into such code and bails out
with whatever information it can.
For cases where the class in question is observable
(e.g. class Foo : LiveData<Foo>), we crash with a message since
data binding will try to create foo.getValue().getValue()...

For cases where it is a normal class (which we won't try to unwrap),
we work as desired.

There is possibly more of these but i can only reproduce these 3
cases so didn't want to overzealously add more coverage without
having a repro case.

Bug: 141633235
Bug: 140999936
Test: RecursiveLayoutTest (TestApp), RecursiveObservableTest
(compileation test)
Change-Id: I9977a1c8ae7c726b924550783d48049e89ca227c

0 files changed, 0 insertions, 0 deletions