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`

Makes it more clear that this isn't vf-core's heart, but rather a rollup for css, js

Add notes on versioning of components

Modularise fractal config for reuse as `require`

Add missing npm files 

Overlooked a couple silly things.

This makes the fractal config reusable across the various ways we're looking to consume fractal; some freatures added/needed:
-  adds a callback so we can know when fractal has fully strapped and `fractal.components` is ready
- we can ask for a build or server instatation
- pass in where fractal should look for components

This means we'll be able to: `const vfFractalBuild = require('@visual-framework/vf-core/fractal.js).initialize('server',fractalReadyCallback);` in things ranging from Eleventy to child pattern libraries.

HOTFIX - Pass missing param to codeblock extension

not having it stops the codeblock extension from working.

COMPONENTS - alpha.4-updates 

Fix naming of fonts on npm

* vf-simple-search is actually vf-search

* Single quotes

* Import vf-link--secondary colour to vf-summarry

Was issuing an error. Strange it didn't show up before.

* Add "pattern" and "component" guidance

* Swap a selection of "pattern" for "component"

* Missed a couple files to commit

* Somehow vf-colors.map.scss was deleted

* Referecne `components/vf-core-components`

This doesn't affect vf-core particuarly, but will affect vf-child-template

* Fix a build error/warning

Not sure when this started happening; was erroring but continuing:

> ⚑ Exported 351 of 910 items
> ✘ Failed to export url /components/detail/vf-button--sizes - (/Users/khawkins/Documents/GitHub/vf-core/tools/vf-frctl-theme/views/pages/components/detail.njk)
>   Template render error: (/Users/khawkins/Documents/GitHub/vf-core/tools/vf-frctl-theme/views/partials/pen/preview.njk)
>   Error: Unable to call `entity["variants"]`, which is undefined or falsey

* updates masthead to be nearer what we need

* updates mark for generic masthead

* adds custom properties to design tokens task

* adds css custom properties files

* alters the HTML to use 'default' custom properties

* adds css custom properties

* whitespace

* adds css custom properties

* updates CSS fallbacks for older browsers

* Update npm-shrinkwrap.json

* Documentation: Add comments on properties and token file location

This is both related to the active PR and a general improvement to "don't edit this file, go edit the design tokens instead"

* Chore: Rund design token task on build

Should help fight entropy with design tokens possibly getting out of sync from Sass

* Clean up a file generation mess

* Add further comments, template refinements

* Fix indentation linting

* changes the wording so it's simpler, fixes some whitespace annoyances

* updated gulp tokens results

* removes IDs that came from the WP list

Doc cleanup