Update examples to run independently

[mefellows]

Currently, all of the examples run with the implicit parent package scope, as well as requiring a compiled build of pact-js to run (i.e. a npm run dist in the root directory).

This makes it difficult for newcomers to navigate to an example and run independently, or to use as a basic for a project because the dependencies are not made clear.

This change does the following:

• Moves the karma examples into the examples, because it just makes sense to do so
• Uses the exported versions of the pact packages (as one would do in real life)
• Adds all required packages to each example to enable independently installing
• Updates the travis build to use npm link so that all examples in the repository are still tested against the current build of Pact JS / Pact Web, to prevent bugs/regressions

[coveralls]

Coverage remained the same at 95.041% when pulling 5d0d349 on feat/examples-use-exported-packages into d10e4b1 on master.

[coveralls]

Coverage remained the same at 95.041% when pulling 24101e1 on feat/examples-use-exported-packages into d10e4b1 on master.

[TimothyJones]

I love this! Great improvement.

A few small things:

1. Snyk complains about the examples. I wonder if we can/should prevent it from checking them?

2. I hadn't realised the graphql example is written in typescript - a quick glance suggests there's a fair bit of extra config that's unrelated to the example. Should we change this in a later commit?

3. Some of the bash changes are missing ", and for robustness, it's probably worth covering if the glob doesn't match (I'll push a commit fixing these).

[mefellows]

Thanks.

1. Yes, probably a good idea (or we can just let the updates come through and fix them?)
2. There's not a lot of consistency in the examples, I'd love to see a consistent use case used throughout (where appropriate). See Examples are too contrived to be useful #179 for some ramblings on that.
3. Thanks, that would be appreciated. I'll wait for this before merging.