Fixing the Fork creation over API on Canary & co

What does this MR do?

It fixes a test that was failing only on Canary and Production. The reason for this was explained in the issue #343396. To fix this test for now, I have added a manual log out and log in on any dotcom environment. This needs to be changed as soon as the linked issue is resolved. It was not finished in this MR since the amount of work was increasing and preventing the fixing of this test. It also needs more works since it is touching much more than just this single test if not done correctly.

E2E Test Failure issue(s)

• The Failure Issue: #342599 (closed)
• The Follow-Up Issue: #343396

Check-list

• General code guidelines check-list
  • Code review guidelines
  • Style guides
• Quarantine test check-list
  • Follow the Quarantining Tests guide.
  • Confirm the test has a quarantine: tag with the specified quarantine type.
  • Note if the test should be quarantined for a specific environment.
  • (Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
• Dequarantine test check-list
  • Follow the Dequarantining Tests guide.
  • Confirm the test consistently passes on the target GitLab environment(s).
    • (Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE variable from the package-and-qa job of the current merge request.
• To ensure a faster turnaround, ask in the #quality Slack channel for someone to review and merge the merge request, rather than assigning it directly.