Migrate CollectionViewHolder to Compose

[gabrielluong]

Breakage of #22755

This refers to:

• CollectionViewHolder showing an individual collection. (maybe instead of adding individual composables to the homescreen for each collection we could wrap them all in a list)

The compose versions can be added to the current RecyclerView but before doing so we should ensure there will be no performance regression introduced.
To profile the differences the steps from #21854 (comment) can be used.

┆Issue is synchronized with this Jira Task

[Mugurell]

Migrating this to compose allows us to also simplify the current approach of adding having collections and collection items as separate viewholders on screen. (CollectionViewHolder plus one or more TabInCollectionViewHolder).

Since a collection contains a list of tabs the migrated to compose Collection can also be an expandable list of CollectionTabItems.
This would allow the expand/collapse animation be handled in the Collection composable and as such be smoother (and simpler), not having to sync the rounded corners like it's being done now (but buggy) between CollectionViewHolder and TabInCollectionViewHolder and also avoid checking whether one tab item is the same as another, a cumbersome check that is again buggy, all these seen in the following recording:

CollectionsIssues.mp4

cc @gabrielluong

[gabrielluong]

I would prefer to see the migration to use a LazyColumn in #24316, which will display the list of collection items. I think we want an incremental approach just focus on the CollectionViewHolder which only contains the expandable header first to evaluate what is the extent of UI test failures and how do we coordinate with the release schedule and QA testing team to mitigate risk and fixing any breaking tests. Converting CollectionViewHolder will already include quite a bit of functionality - share, menu, expand. I am also anticipating other challenges like handling the existing selected border code, so I think there are plenty of things to cover here.

This is not to say we shouldn't convert everything to Compose, but to do it in reasonable steps so we can review the code more easily and evaluate the risk.

[Mugurell]

@ QA: This was migrated to Compose but should look and behave the same as before.

[SoftVision-LorandJanos]

Verified as fixed with the latest Nightly 102.0a1 (2022-05-18T17:12:12.001240).
Devices used:

Samsung Galaxy Tab S3 (Android 9).
Google Pixel 4 (Android 12).