Fixed: React lint warnings

[drikusroor]

This PR intends to resolve the React warnings as described in #598

@BeritJanssen the remaining linting errors are all react-hooks/exhaustive-deps, e.g. "missing" or "incorrect" dependencies. Now, eslint proposes fixes here, but I'm not completely aware of what happens and should happen exactly so I'm afraid to break stuff, and I don't want to risk that over some linting warnings. Perhaps you can look into these or we can look at them together in the future?

[BeritJanssen]

Thanks for configuring the linter. I think that indeed we should review the missing dependencies for the hooks manually. #648 should fix some of those warnings already.

[BeritJanssen]

I think we can merge some of these adjustments by the linter already, and take care of the missing / incorrect dependencies in the react hooks later. Perhaps as a team we should review our linter settings, since I'm not sure everyone has one configured.

But please undo the change removing finalizeSession from API.js and Final.js. Indeed, I see that finalize() is never called, while it should probably be placed into the useEffect hook as a cleanup function.

[drikusroor]

I think we can merge some of these adjustments by the linter already, and take care of the missing / incorrect dependencies in the react hooks later. Perhaps as a team we should review our linter settings, since I'm not sure everyone has one configured.

But please undo the change removing finalizeSession from API.js and Final.js. Indeed, I see that finalize() is never called, while it should probably be placed into the useEffect hook as a cleanup function.

I've looked it up and you have updated the call to finalize on June 20 here and made the div into a a element: 1cc4ac4#diff-dd2727c4ba071122a678bb23e7b9b2833fd33ab5995321f1df7d3dc4f4523d33

I think then it got removed after merging develop into a feature branch while resolving conflicts and so on:

1cc4ac4#diff-dd2727c4ba071122a678bb23e7b9b2833fd33ab5995321f1df7d3dc4f4523d33

Apart from that, I don't know if it ever behaved like it should have? I can imagine when you click a link that also has a onClick handler, race conditions might cause the onClick never to get executed or finished as it already navigates towards a new page.

[drikusroor]

I will merge this and I've addressed the finalize session not being called as a seperate issue in #676 !