Run tests without subprocess and split tests and examples

[dapplion]

🦅 Pull Request

Builds on #1099.

• Instead of calling a node script via a subprocess, the example guide is run directly within node, which provides better debugging and clarity.
• Test runs are divided into two NPM scripts npm run test and npm run test:integration. It can make sense to not run the examples test on the git hooks, and run them only on CI. We could also skip coverage for the guides / examples with a similar technique

🚨 Test instructions

npm run test:integration

[0xGabi]

Suggested change

	const ensRegistryAddress = '0x5f6f7e8cc7346a11ca2def8f827b7a0b612c56a1'
	const options = {
	web3,
	provider: web3.eth.currentProvider,
	ipfs: {
	rpc: { protocol: 'http', host: 'localhost', port: 5001, default: true },
	gateway: 'http://localhost:8080/ipfs',
	},
	registryAddress: ensRegistryAddress,
	ensRegistryAddress,
	'ens-registry': ensRegistryAddress,
	}
	const options = {
	web3,
	provider: web3.eth.currentProvider,
	apm: {
	ipfs: {
	rpc: { protocol: 'http', host: 'localhost', port: 5001, default: true },
	gateway: 'http://localhost:8080/ipfs',
	},
	ensRegistryAddress: '0x5f6f7e8cc7346a11ca2def8f827b7a0b612c56a1',
	},
	}

[0xGabi]

Suggested change

	apm: options,
	apm: options.apm,

[0xGabi]

Suggested change

	options
	options.apm

[0xGabi]

The option object was a bit awkward. Also in the example only the apm configuration was utilized. Do we want to remove the provider and web3? 🤔

[dapplion]

The option object was a bit awkward. Also in the example only the apm configuration was utilized. Do we want to remove the provider and web3?

@0xGabi I agree, the option object is awful but that's what's required right now to make it work. This should be used a hint to improve the interface / API of the toolkit.