SR-454: Improve development env w/ Jekyll & Docker

[GormFrank]

Everything is this PR is related to the local development setup, and has no impact on the distribution files. Its purpose is to improve the repository to facilitate contribution and testing. As part of this PR, you'll see that:

• You can now run a test website locally with Docker.
  • It uses an existing image which comes in handy for running Jekyll on a local server bretfisher/jekyll-serve.
• The docker website leverages the remote GCWeb Jekyll theme.
  • Uses a newly added front-matter option for scripts of type module.
• The website hosted on local server updates itself upon changes to the HTML, CSS and JS files.
• Search pages work as expected thanks to a new approach with adding an API key as a Jekyll site-wide data variable.
• It still allows you to build distribution files with linting and other code quality checks with Grunt.
• It still allows you to spin up GitHub pages on your fork (please do not expose the API key, use the token alternative instead).
• Improved documentation to guide developement work.
• Expansion of test pages to include more use cases such as overriding templates for custom ones, as per the maintenance plan forward.
  • I use test/qs-en.html and test/qs-fr.html to test PR Various updates including Query Suggestions #28.
• Enforces the line ending for CSS build to be linux line ending in the distribution file, as per the maintenance plan forward.

Consequently, this PR has the following relation to other PRs:

• Is dependent on GCWeb's PR 2474 to be merged prior to merging this one.
• Is related to PR 10 in Service Canada's internal documentation website (not dependent).
• Is a prerequisite to merging the PR Various updates including Query Suggestions #28 for Query Suggestions and other changes.

[duboisp]

Reviewed quickly and it looks good to merge.

Comment: There is a possibility to simplify the UI by moving the use of CSS utilities class directly managed via the page master CSS class "page-type-search"

[GormFrank]

Reviewed quickly and it looks good to merge.

Comment: There is a possibility to simplify the UI by moving the use of CSS utilities class directly managed via the page master CSS class "page-type-search"

Thanks for bringing this up, it is in fact on the to do list, but here you are providing an insight on where to start with the CSS selector, and thank you for this.

---

Based on technical discussions and on the fact that this PR does not affect the distribution files, I will be self-merging.