React Navigation v6.

I'm updating to RN 0.63 instead of the latest (0.66 at the time of this writing)
so we can update the navigation related libraries to their latest versions, and
then proceed with the larger leap towards the latest RN.

* fix(TPC): Implode the simulcast group only after toUnifiedPlan conversion. This fixes a regression introduced by the previous commit.

53b9601689/...adf2f15d0045747ba609b1fe19c088841717da11

* fix: still show menu to toggle self view if disableLocalVideoFlip

* fixed lint issues

allows chat button to be displayed when there should be enough space for it

* ref(TPC) Cleanup and fix formating.
* ref(TPC) Remove an unnecessary toUnified sdp conversion. sLD is called immediately after createOffer/createAnswer, therefore the desc provided by createOffer/createAnswer can be directly passed to sLD without the need for converting it to unified plan format. This also fixes a warning seen on the browser console that says 'The description does not look like plan-b'.
* fix(tpc) extend ulpfec workaround to all versions
* fix: check if chrome version > 95 instead
* Fix issue number for rtx ulpfec workaround
* fix(tpc) disable ulpfec on chrome 97

55a03ac1b5/...53b96016893088824621ceacc721e6ba912bdb99

In case of slow resolving gUM, we can join the call (quickly joining from pre-join screen) and the gUM will be resolved after we receive the start A/V muted from jicofo and will produce a source-add, joining unmuted ignoring jicofo.

When gUM is slow, and we quickly join the conference, then startWithAudioMuted was not respected.

Upstream now skips the callback, so we need to provide one.

Also, ignore the toggle screenshare shortcut when the video sender limit is reached.

https://google.github.io/mediapipe/solutions/models.html#selfie-segmentation

- add possibility to allow execution of the button's routine besides triggering
`toolbarButtonClicked` API event
- keep backwards compatibility
- get rid of `ToolbarButton`