Default view with Translator Skills

Hi everyone.

First of all thank you for the work in this module, that provides a very useful functionality.

I have been checking the module just to test it, together with translators to use the translation skills, installed with the Umami profile with a third language. I have been trying to use the default view with a non-admin user with some problems, and I don't know exactly if any of the local changes are responsible of them, or maybe it's about this module or the translators one. Thing is, the user created for the test have the translation skill for English to German (the third language), and the `Create translations (in translation skills)` permission. When accessing the view, in English, the operations never showed the create translation button and, debugging, what I saw is that the function `getTranslationAccess` calls the same function in the AccessHandler just passing the entity and the operation, without the source or target langcodes. Then the `TranslatorsContentTranslationHandlerTrait.php` (I understand that this is part of another project, so if I should ask in the other issue queue please just tell me), given that it doesn't receive the codes, check for the route and, after that, just use the current language, and checks for English for both the source and target language for the translation.

What I did to make it work was to change this in `src/EntityTranslationInfo.php`:

public function getTranslationAccess($operation) {
    $sourceId = $targetId = NULL;
    if ($this->sourceLanguage instanceof LanguageInterface) {
      $sourceId = $this->sourceLanguage->getId();
    }
    if ($this->targetLanguage instanceof LanguageInterface) {
      $targetId = $this->targetLanguage->getId();
    }
    $access = $this->accessHandler->getTranslationAccess($this->entity, $operation, $sourceId, $targetId);
    return $access->isAllowed();
  }

But I understand that may not be the best solution, given that the `ContentTranslationHandlerInterface` defines the getTranslationAccess with just two params, even if for the submodule the implementation accepts four.

Did I do something wrong? If not, maybe adding the two extra params would be ok? Or should I write an issue in the translators issue queue?

Thank you :-)