Synthetic test data

[schovi]

@rathonit1

For now, I think it can be 2 - 3 swagger files which represent different APIs with different features. Then 2 or more blueprints based on different scenarios for each swagger file. And package blueprints based on that and with different scenarios.

With this, we can simply duplicate them by changing part of name and path and then reuse them as we wish.

Usage:

1. Unit tests of functions
2. Integration tests with real calls to Mashery, which will be cached and stored for replaying without touching Mashery again. There are awesome libs for that https://github.com/adidas-group/mashery-toolbelt/blob/5a1a74216e7c250050efa2de81486819114e4049/test/workflow/adidas/resolvePackageBlueprint.test.js#L8 This tests would be most simple.
3. I think we can have some "manual test" which will create everything in Mashery and we can check it manually.