Convert some files to TS
Move some styles from SCSS to JSS
Update design

Remove unnecessary @ts-ignores
Remove unnecessary eslint-disable

Starting chrome 107, the recorder does not record any data if the audio stream has no tracks
To fix this we create a track for the local user (muted track)

feat(base/ui/native): replaced react native TextInput component with our native Input component

Remove unused icons
Remove fill none from icons
Rename some icons

Remove global variables from files
Change type to interface

Show the start recording notification on jicofo update only. This way
the initiator will be available and we will be able to fetch and display
recording link and send iframe API event.

Remove unnecessary ts-ignores
Remove unnecessary eslint-disable
Fix type errors
Change Dispatch type to IStore['dispatch']

We have observed that participant audio is distant and garbled, so we
added the tracks individually to the mixer.

In addition, using tab audio prevents us from using preferCurrentTab due
to: https://bugs.chromium.org/p/chromium/issues/detail?id=1317964 so
losing audio effects but having better participant audio quality (in
addition to better UX) is not a bad compromise.

Convert some files to TS

Remove @atlaskit/dropdown
Convert some files to TS

Remove unnecessary ts-ignores

Use new TS config from @jitsi/eslint
Fix all lint errors

Remove unnecessary ts-ignores
Change any to actual types
Fix eslint rule

Create IStateful interface
Use IState interface everywhere
Remove unnecessary @ts-ignore

Convert files that use material-ui to TS (needed for material-ui upgrade)

* feat(base/native): Switch thumbColor and trackColor default props

Bring Switch component more in line
Convert some files to TS

* feat(recording): StartRecordingDialogContent web and native

Bring web and native more in line

The new behavior is as follows:

IF a user has a token and `features` is not set, we treat it as if the
feature was enabled.

IF a user has a token and `features` is set, we check if the feature
name has a value of "true".

`isJwtFeatureEnabled` also provides a way to specify the default value
in case there is no token.

The web and mobile Button components are not implemented the same way
and this came to bite us.

This is a stopgap fix, the real fix needs to be to make them have
exactly the same shared props and behavior.

Overwrite the new flag with the old one only if the new one is not set
Fix hideStorageWarning config