Fix Control API gRPC gen files unexpected regeneration

[evdokimovs]

Synopsis

When working with medea-jason project, sometimes when you run something like cargo check, files related to the Control API gRPC are regenerated. And some files can be deleted and this can be accidentally committed to the branch. This changes are not correct, because this files should live in the git index, but because of the feature flags, they're regenerated incorrectly.

Solution

We can just add server and client features to the default set of features of medea-control-api-proto crate. So when we run cargo check without any arguments, it will compile with this features. This will not remove required files. This fix works, but it needs to be checked, because it can cause some unexpected behaviour.

Checklist

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

[evdokimovs]

Fix Control API gRPC codegen files unexpected regeneration (#168)

[evdokimovs]

It was fixed in #170