Development: Fix issue where the VCS token is not present for some users after logging in

[chrisknedl]

@coderabbitai ignore

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data.
• I strictly followed the client coding and design guidelines.
• I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
• I documented the TypeScript code using JSDoc style.

Motivation and Context

This issue was initially discovered when a user participates in an exercise for the first time after being created, in which case the VCS access token might be missing, and therefore the resulting repo URL is not correct and cannot be used to clone the repository. This PR fixes this problem and other related issues that might possibly still be undiscovered.

Description

To fix this issue, the user caching mechanism not only checks if the user object is initialized, but also if it contains the token when one is expected. If not, the user is fetched from the database.

Steps for Testing

This issue can only be reproduced with old accounts that were present before the vcsAccessToken feature was activated. Because of this, the PR also doesn't change anything for the test servers.

What you can check:
On any test server check that the clone URL is still shown when participating as student in a programming exercise. Ideally one test for a testserver connected to GitLab/Jenkins and another one to either Bamboo or LocalVCS.

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked

Review Progress

Performance Review

• I (as a reviewer) confirm that the client changes (in particular related to REST calls and UI responsiveness) are implemented with a very good performance

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage