Add initial setup for Spec of Specs generator

[2snEM6]

This PR introduces a draft initial setup to approach Spec of Specs test generators.

The purpose of this PR is to setup the structure for a future implementation and for that reason, sample generators have been added.

Please note that as for now, those generators under (generators) folder may contain bugs or inconsistencies.

Note: Header includes common properties for all generator outputs:

• title
• summary
• config
• runner
• handler
• test_cases (the content is independent to each suite)

The following folder structure has been created under the root repo folder.

- generators
	- base_generator.js
	- type_name
		- README.md
		- index.js

- generator_outputs (tmp default format)
	- type_name
		- handler_name.json

- config
	- network_name.json

- utils (common logic)

How to manually test it?

$ cd protocol-specs
$ nom run generate-all-specs

This will create a folder generator_outputs where you will be able to find all the test suites.

Review checklist

• The PR resolves #INSERT_ISSUE_NUMBER
• All new code is covered with unit tests
• Relevant integration / functional tests are added
• Commit messages follow the commit guidelines
• Documentation has been added/updated

[shuse2]

Probably I made the confusion, but if it's standalone, base branch can be development

[nazarhussain]

@limiaspasdaniel @shuse2 Suggestion: If we keep the specs of specs inside same repo as formal implementation, then we may be using same implementation to generate specs (data sets) for those specs(acceptance criteria).

Would be nice if we completely it separate and keep far away from implementation.

[shuse2]

@nazarhussain I agree it would be better to separate the repository.
I think we can separate the repository in the future, as it would be easier for now to manage everything in one repo.