
In most cases, the places that were trying to avoid a transitive dependency on `lib-exoplayer` when this duplication was introduced [1] are already depending on it again, except for `lib-container` where the dep is added in this change. In general it seems fine for the tests of module A to depend (transitively or directly) on module B even where the prod code of module A **does not** depend on module B. [1] <unknown commit> PiperOrigin-RevId: 561660371