Refresh data

[PhlexPlexico]

This PR is aimed at including some auto-pulls using setIntervals in two parts of the application. The first is in the player stats per map, which should allow us to poll data and view the scoreboard without having to refresh the page. After five seconds, users are allowed to force a refresh for the data, since we would like to have a bit of a wait time so spamming is not an option.

The second point of this PR will be to try and attempt to refresh vetoes as well. However, there's not an easy way of determining if a match is complete, or has vetoes without making more API calls. So the next step is to determine if we can find a way to ensure a match is running, and has a veto process, and check to see if they are in that state. One way of doing this is to maybe create an API end point that pings the match and gets the status of the server, and the other is just using different API calls to determine if we have vetoes or not. Still need to think on this a bit more.

Closes #118 #119

[kubo6472]

since the last update, the order of the matches and everything is getting really messed up.

this is after I click on the match id to sort them, default is even worse

[PhlexPlexico]

This is most likely due to the synchronous loading from the data into the table. I'm no front-end developer so this will take some time to fix :) I've been looking at it, but not sure how to adjust it.

[PhlexPlexico]

I think an easier way to fix this will to be create some new routes that just give the data that it's trying to assemble on the front end, that may help with ordering values... May look into that as a next avenue of trying to fix this.