Initial working site implementation.

[MichaelPachec0]

This PR will merge into the master branch a working implementation of the site. This is still a WIP as i have not committed the whole site and (The code has been committed already) There is still the question of what to do when the user gets a full score. (will be implemented in another PR). For the moment the following things are functional:

• [X] Back-end loads.
• [X] Proper Webpage (along with css/js/img) gets sent to the client when requested, the modal (thanks to @thecornisians) is also here with proper attribution.
• [X] The api works and when a new game is requested and when you need to compare cards (for the moment it will only compare urls as the implementation was simple enough to create, this can be changed in the future).
• [X] Node packages have been frozen in anticipation of deploying on a Provider.
• [X] Fixes #59 where an version of node-fetch was vulnerable, in regards to this web app this is not something that is affected by this, but there is no point in carrying a known vulnerable package, and i have tested the new version to work.
• [X] Fixes #48 with a new async function grabCards and a Handler function called cardHandler.
• [X] Fixes #28 and keeps score locally (The process to add to the score is done on the server so there are still requests done). Is possible if wanted to make the score be completely server side.

[MichaelPachec0]

As of now this is all the work i have done. The last item still needs to be done for which i will try to get to today.

EDIT: In the future i might change a portion of the api to use a POST request (for example checking if the user should get a point)

EDIT 2: I will probably limit the pr to this and create the another that handles the winning condition in another. This already has a ton of changes that will make it difficult to review.

[MichaelPachec0]

LGTM, one thing, however, from what I recall the API returns an ID for each pokemon card. in the form of an array of objects, each object containing data on the card, and one of those properties being an ID.

The only problem is the client does not retain that info. I could have made that change (keeping the id) either keeping in JavaScript or putting it as a element attribute, but as you can imagine it would have created more changes (and more code commits). Id be more than happy to create another issue (or have anyone else create an issue tracking this) but i would want to keep that seperate to this PR.