Refresh owner user/copilot Gitlab access token automatically when needed

[gets0ul]

#447

[52cs]

@gets0ul Good bug fix!
But the topcoder-x-processor will also need to use the owerUser's access_token. You should also call refreshGitlabUserAccessToken in topcoder-x-processor whenever the user token is used.

Even this way, the access_token will also expired if the use interval of the access_token is larger than 2 hours.

const setTimeoutRefreshGitlabUserAccessToken = () => {
    refreshGitlabUserAccessToken();
    setTimeout(() => setTimeoutRefreshGitlabUserAccessToken, 3600*2-300);
};

The most elegant way should be add setTimeout(() => setTimeoutRefreshGitlabUserAccessToken, 3600*2-300); at the end of ownerUserLoginCallback.

[gets0ul]

@52cs It's fine, I think. No need to use setTimeout to do it periodically as refresh_token can always be used even if access_token is already expired.

[52cs]

@gets0ul

1. refresh_token also has expired time.
2. When process Issue related events in topcoder-x-processor, refreshGitlabUserAccessToken does not called.