* added tests
* Added test
* Implemented support for named 'pipelines' property in pino.transport
* Updated pino.d.ts and api.md to include pipeline within targets
* - Reverted changes related to the support of named pipelines
- Implemented support for mixed target&pipeline definitions within `targets` in `transport.js`
- Merged logic from both `worker.js` and `worker-pipeline.js` into `worker.js`
- Fixed `pipeline.test.js`
- Fixed docs to reflect changes above
TODO:
- Remove `worker-pipeline.js`
- Fix `transport.js` to use only `worker.js`
- Fix related docs
- Fix UTs
* - Removed `worker-pipeline.js`
- Updated docs to remove mentions of `worker-pipeline.js`
- Fixed failing UTs
- Fixed `transport.js` to use only `worker.js` also when `pipeline` is defined
- Fixed `worker.js` to work properly when only `pipeline` is defined
* added a simple flow schema to worker.js
* added a simple flow schema to worker.js
* Added a special case in worker.js to skip the multistream instance when a single target or pipeline is defined
* - Added optional 'level' property to TransportPipelineOptions interface
- A level can now be defined for pipelines defined inside 'targets'
- Added UT in 'pipeline.test.js' to check expected behaviour with 'dedupe'
* add option to pass down custom levels to multistream
* fix types
* update docs
* add test for types
* combine custom with default levels when useOnlyCustomLevels is not set
* add tranport test
