Description
The command has to support 2 output format:

1. human friendly output: tree representation with component information (not the entire component descriptors)
2. machine readable: flat list in yaml or json
   For the machine readable format, it is particularly important to preserve the original ordering (established in ocm v1).

Instead of making the --recursive a boolean, we make it a int with:

• -1 = infinite recursion
• 0 = no recursion (default)
• >0 = level of recursion (this will not be available for starters, but the API will still be open for this)

Internally, the recursive fetching of components will built on the resolver config.

Done Criteria

• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Enduser Documentation updated (if applicable)
• Internal technical Documentation created/updated (if applicable)
• Successful demonstration in Review