The Translate tab is shown even though the logged-in user doesn't have the permission to translate content

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

Think this is very close!

For the ContentTranslationOperationsTest tests can we some additional assertions.

$node = $this->drupalCreateNode(['status' => FALSE, 'type' => 'article']);
Think this should be $article_node

Then a basic_node should be created.

Then during each user test should make sure they do have access to things but think we should also check to make they don't have access to other things.

Example if I have access to all can we check both content types
If I have access to just articles can we check that and check I can't translate basic pages.

Re-rolled for latest 10.1.x.

The tests in #90 don't apply on Drupal 10.2.3, I removed them for now.

Re-rolled for latest 11.x.

I am working on adding back the tests that were removed because they no longer applied in #91. I'm running into a problem where, in core/modules/content_translation/tests/src/Functional/ContentTranslationContextualLinksTest.php, an operation is tried with an admin user on admin/config/regional/content-language but even though $this->drupalLogin($this->rootUser); has been run, the HTML output states that the user has no access to the page.

I'm wondering whether the new Super user access policy could have something to do with this problem, but from what I've been able to deduce so far, the services.yml in use for these tests is the default.services.yml in sites/default and that has the policy set to true, meaning UID 1 should still be all-powerful. I would be grateful for assistance as this is currently blocking me from advancing with the tests.