259 homepage infinite scrolling

closes #259

What is it supposed to do
When the user has fetched all posts on the homepage, scrolling further would repeat the same process to allow infinite scrolling.

How can we test your branch
Go to the homepage and scroll down. See if all posts that should be fetched are properly fetched and displayed again.

1. General checklist

[x] a. Tested happy flow.
[x] b. Tested unhappy flow.
[x] c. No unexpected exceptions.
[x] d. No code with high complexity. (Big O)
[x] e. EOF newline.
[x] f. No floating comma's and spaces.
[x] g. No unexpected/unhandled errors.
[x] h. Lines no longer than 'guideline' in IDE.
[x] i. Correct indentation.
[x] j. No usage of legacy functionalities.
[x] k. (JS) Curly braces on the sameline as reserved keywords (if () { instead of { on line below)
[x] l. (JS) No double quotes.
[x] m. (JS) Single newline above unique code structures and reserved keywords.
[x] n. (JS) Variables bundled where possible.
[x] o. (JS) No semi-colons except where they have a functional necessity, such as for-loops.
[x] p. (JS) No code that is meant exclusively for development, such as console.logs for data preview.

2. If relevant, front-end checklist

[x] a. Responsive. (Desktop all the way to mobile 320px)
[x] b. Using SCSS variables where relevant.
[x] c. Relevant class names
[x] d. No modified global SCSS properties, except if necessary and fully tested the impact.
[x] e. Checked caniuse for more modern CSS properties.

3. If relevant, back-end checklist

[ ] a. No unhandled promise rejections.
[ ] b. Seeders still functional.
[ ] c. No primary-key violations.
[ ] d. Normalization, atleast 3NF.
[ ] e. Used guards (middleware) where necessary and tested if route is guarded.

4. If relevant, test these browsers

[x] a. Chrome
[x] b. Firefox
[ ] c. Opera
[x] d. Edge
[ ] e. Safari

AjobK / Seaqull

259 homepage infinite scrolling #275