* Add dynamic sass imports

Use case: right now if a component isn't "installed" it _must_ be disabled in vf-core/index.scss

That adds a configuration step to customisation and means you can't really ever npm install vf-core unless you want to not add/remove components (which, you really should be customising)

So this idea uses gulp+node as a middle layer to see what components are installed and then ignores them in `vf-core/index.scss` if they're missing.

WIP and it needs cleanup.

* Quick tidy

* Cleanup, better warnings

* updates vf-blockquote to use yaml and adds id/class overrides

* a little blockquote fix

* updates buttons to use yaml to generate variants

* updates divider to allow for overiding classes/ids

* updates figure to allow for overiding classes/ids

* updates logo to allow for overiding classes/ids and use of data

* update vf-list to use YAML

* a refactor of the initial templating for vf-heading

* updates vf-text to make use of taml data and nunjucks logic

* Add http before link

Features/markdown filters

adds initial autocomment bot things

documentation: governance text #114

Refactors vf-link to use yaml and break out the disabled state.

* Optimise gulp dev

Avoids a lot of thrashing in the generation, optimisation, and watching tasks. This was particularly painful on slower machines.

* adds command for fractal to ignore sass file changes to stop a reload of the page

* updates ignored path for Fractal watch to match gulp watch path

* updates vf-badge to use yaml more and leave the nunjucks nice and tidy

* vf-badge nunjucks macro-fication

* vf-badge nunjucks macro-fication

* Fixed that for you 

* updates vf-badge to un-macro it

* updates vf-badge to all the new things

* updates vf-badge to all the new things

* updates vf-text to use yml / nunjucks more

* sanitises the yaml variables from the component name

* sanitises the yaml variables from the component name and uses new data for rendering list

* adds a vertical pipe for the additional class

* updates box

* article meta

* starts on buttons

* changes buttons mixin

* makes a start on summary

* Typos

- Makes `overide` to `override`
- Adds "https://" before demo links

CHORE - npm file tracking

fix: support passing "false"

Was using an insufficent way to pass "false" and a typo. 

fix: npmignore files and version

Had a typo in the version name and the .npmignore should have been ignoring more things (seems it does not overlay with .gitignore)

component: deprecation-example

For #336

fix/font-component-naming

Somehow commits in #330 were partly reverted 

* removes vf-contact pattern, replaces by vf-summary--profile

* removes the @import in vf-core

* removes vf-job-description

* updates template to use vf-summary--news instead of vf-news-item

* removes vf-news-item

* cheeky double vf-vf- removed

* removes vf-snippet

* sneaky change to correct documentation

* updates to remove vf-data-protection-banner as we are using vf-banner--gdpr

* updates to remove vf-factoid as we are using vf-box--factoid

* removes vf-tag as we are using vf-badge

* Chore/deprecation documentation (#347)

* documentation: deprecation

* added another step

I think once we've done all the codebase deprecating we need to push a release - so that if a project ends up re-installing something deprecated it gets all that information in the project. If that makes sense :D

ENHANCEMENT - vf-core npm optimisations

Allows passin of theme, build, and browser open options.

Will need to move all these options into a proper config setting in a new PR.

- matches repo name
- consistent with the logic that vf-core is part of the visual framework "system"
- adds npmingnore so you can `npm install vf-core`