Implement tracks disabling/enabling on subscribers side (#27)

[evdokimovs]

Part of #27

Synopsis

For the future PRs we need to implement remote Senders muting/unmuting.

This methods will be added to the JS-side Room:

1. Room.mute_remote_audio

2. Room.mute_remote_video

3. Room.unmute_remote_audio

4. Room.unmute_remove_video

Solution

Send Command::UpdateTracks with remote TrackIds of the all Receivers with some kind.

Store remote mute state in the Jason Room and consider it on Event::PeerCreated receiving.

Checklist

• Created PR:
  • In draft mode
  • Name contains Draft: prefix
  • Name contains issue reference
  • Has k:: labels applied
  • Has assignee
• Documentation is updated (if required)
• Tests are updated (if required)
• Changes conform code style
• CHANGELOG entry is added (if required)
• FCM (final commit message) is posted
  • and approved
• Review is completed and changes are approved
• Before merge:
  • Milestone is set
  • PR's name and description are correct and up-to-date
  • Draft: prefix is removed
  • All temporary labels are removed

[evdokimovs]

FCM

Implement tracks disabling/enabling on subscribers side (#127, #27)

- expose methods for muting remote audio/video on Room API in Jason
- add remote audio/video muting to the 'e2e-demo' and 'demo' apps

[evdokimovs]

Waits for merging:

• Automate test names generating in the E2E tests (Automate test names generating in the E2E tests (#27) #128)
• Improve Jason logging (Use 'log' and 'wasm-logger' crates for Jason logging (#27) #129)
• Receiver muting before call (Implement Receiver muting before call (#27) #130)
• Abstract mute state machinery logic (Abstract mute state machinery logic (#27) #131)

[tyranron]

And merge wtih the latest master.