prerelease: make demos use origami build service v3 for their dependencies instead of v2

v11.0.0-beta.27

make demos use origmai build service v3 for their dependencies

prerelease: Allow './main.js' to be the browser entrypoint for a component

v11.0.0-beta.26

Add test case for complex browser entry point

prerelease: update all dependencies to latest versions which support commonjs

the aliases and strip-ansi packages have new versions which only support ecmascript modules, which means we can't update to those until we make origami-build-tools' code to use import/export

prerelease: Verify supported npm version is set to a minimum of 7.0.0

This verification helps ensure origami components adhere to the specification

The origami 2.0 spec states:
>It *must* include an engines property set to an object which has an npm property set to a SemVer range which disallows anything below v7.0.0. E.G. ^7 would be valid as would >= 7.

prerelease: Enforce that a package.json file exists for origami components instead of skipping the validation

v11.0.0-beta.23

ensure the test directory does not exist before we try to create it

prerelease: Ensure that origami components have package.json.type set to 'module'

v11.0.0-beta.22

Ensure that origami components have package.json.type set to 'module'

prerelease: Make verify-origami-json look for all the different origamiType variations

v11.0.0-beta.21

Make verify-origami-json look for all the different origamiType varia…

prerelease: Add validation for package.json.browser field

The component v2 specification states that if a main.js file exists, then the `browser` field must be set to `"main.js"`. This commit updates the verify task to ensure that the component being tested adheres to these rules.

I've quoted below the parts of the specification this is testing.

>  - It **must** include a <a href="https://docs.npmjs.com/cli/v7/configuring-npm/package-json#browser">`browser`</a> property set to the component's main JavaScript file (`main.js`) **_if_** it exists.

Those came from the spec v2 pull-request -- https://github.com/Financial-Times/origami-website/pull/273/files#diff-5ebc2f3b798414ec905f3fdceb910557607b8d779a56bf1ce09ad48e32fd085aR88

I've also added in a check for the opposite situation, if no `main.js` file exists, then the `browser` field should not exist. This is not currently written in the specification though. If we don't want this functionality, I will remove it. If we do want this functionality, I will update the specification to reflect this.

prerelease: Add validation for package.json.name field

v11.0.0-beta.19

update fixtures to adhere to package.json.name specification

prerelease: Swap to npm-shrinkwrap to ensure all installs use the same dependency versions

v11.0.0-beta.18

Swap to npm-shrinkwrap to ensure all installs use the same dependency…