[BottomNavigationView] BottomNavigationView can have only one setOnNavigationItemSelectedListener

Nobody has claimed this yet.

FEATURE REQUEST

As per title, BottomNavigationView can have only one setOnNavigationItemSelectedListener. This is annoying because if i use the
bottomNavigationView.setupWithNavController(navController)
this internally sets that listener, and i cannot use it anymore for anything else (like setting the text in a custom appBar, for example)
A list of listeners would be the right thing in my opinion.

Ps. this probably applies to setOnNavigationItemReselectedListener(BottomNavigationView.OnNavigationItemReselectedListener listener)
too.

For Pattern reference, see NavController addOnDestinationChangedListener and removeOnDestinationChangedListener

Start by reading BottomNavigationView's setOnNavigationItemSelectedListener and setOnNavigationItemReselectedListener APIs, then compare their behavior with NavController's addOnDestinationChangedListener and removeOnDestinationChangedListener pattern. Done should allow the navigation setup and another consumer to receive the relevant callbacks without breaking existing listener behavior.

Written by the indexing model from the issue text.