Should implement init command to create a standard workspace containing standard workspace structure and standard **provider.yml provisioner.yml tools.yml **

We should have something like

[xx@xx oeWorkSpace]$ tree
.
├── apis
│   └── provider.yml
├── bdsl.yml
├── credentials
│   └── clouds.yml
├── provisioners
│   └── terraform.yml
└── tools
├── json_path.sh
├── json_sort.sh
└── tool.yml

Should have an example of the use of OpenEngine inside of the testing code space

GO lang 1.16, expected to be released in February 2021, will support [embeded files|https://tip.golang.org/doc/go1.16#library-embed] and that will allow moving specification to a cue file instead of having it as a string variable. Having the specifications in cue file will make it more developer friendly.

New version of cue was released and OpenEngine tests are failing. There are changes in cue regarding lists, 'close' builtin and cycle issues. The failing tests return empty list or reference "group" not found.

Add functionality to support the processed returned information

Any operation ( Create, update, delete, read) should have the returned info, this info should be a part of the input, or be put in some file for returned information

We should have a documentation for developer:
something like:

---
Server:
  implicit:
    _memory:
      type: string
    _disk:
      type: string
  providers:
    - action: create
      match:
        type: object
        properties:
          providerType:
            type: string
      parameters:
        imageRef:
          required: true
          explicit:
            type: string

DSL.API:
description: This is the place where stores the path of the api in bdsl.yaml
example:
api:
- provider.yaml
ProviderAPI: (type ProviderAPI map[string]ProviderAPIResources)
description:
below is how ProviderAPI is filled with information
data, err := getSource(provider:TYPE(DSL.API)) //data is the variable containing all provider information from bdsl.yml
yaml.UnmarshalWithOptions(data, &parsedData:TYPE(engine.ProviderAPI), yaml.Strict())
e.AddProvider(parsedData)

ProviderAPIResources:
description:
It has two fields, Implcit:TYPE(map[string]Schema) , Providers :TYPE([]Provider). This is exactly where the information from
provider.yml (inside bdsl.yml) will go via the deserialization

Documentation that should cover the following topics:

• Highlevel description \ Introduction
• The provisioning domain
• Provisioning use cases
• How the engine works
• Interfaces
• Constrains
• Solutions
• Implicit properties
• Decouple solutions
• Resource and solution grouping
• Limitations

The same part for delete and deploy should be refactor into one function to be re-used, there are some redundant code in deploy and delete, they should be refactored into something like
execute(actionName) where actionName can be "create/deploy, delete/destroy,update,refresh" and etc