feat(content-item): add tree command, improved circular dependency import

[rs-amp]

This command allows you to print a dependency tree for any folder of content items on your system. The input directory should contain content items in the same format that the export command generates. It does not require repo/folder layouts, just that all dependent content is contained within the parent directory.

dc-cli content-item tree <dir>

This uses the same dependency tree class as the import task, which uses it to import the deepest content items first so that references can be properly resolved. Here, the "levels" of content items are maintained, and the highest level (most layers of dependencies) is printed first, followed by the lower levels that have not been printed yet.

Each item shows the items that it references or links via a tree structure:

=== LEVEL 3 (1) ===
item1 
├─ item2 
│  └─ item4 
└─ item3 

=== LEVEL 2 (2) ===
item6 
└─ item5 

=== LEVEL 1 (4) ===
item7

When items have been printed before, their name is shown in brackets and their children are not printed. This saves a lot of space on the tree for content items that are reused a lot.

Circular dependencies are a possibility within DC. Like the import task, they are separated from the rest of the tree into a list of "circular dependencies", now ordered by depth to our best ability.

=== CIRCULAR (3) ===
item1 ═════════════════╗
├─ item2               ║
│  └─ item4            ║
│     └─ *** (item1) ══╝
└─ (item3) 

Overlapping circular dependencies with ordering:

=== CIRCULAR (6) ===
item5 ══════════════╗
└─ item6            ║
   └─ *** (item5) ══╝

item1 ══════════════════════╗
└─ item2 ═════════════════╗ ║
   └─ item3               ║ ║
      ├─ *** (item2) ═════╝ ║
      └─ item4              ║
         ├─ *** (item1) ════╝
         └─ (item5) 

This is useful for examining the dependency structure of content that has been created, and identifying potential problems you might encounter when importing content items to a hub. Since circular dependencies are undesirable and sometimes hard to track manually, it's a useful way of identifying them for removal.

This PR also changes the behaviour of importing content with circular dependencies. The circular dependencies are now imported in order of depth first, and should correctly nullify content references that are not yet available. This will not fix required circular dependencies, but it will fix imports for all circular dependencies that do not use required fields.

This PR is built on top of the feature/clone branch. It's in this repo for easier review.

[easen-amp]

Use unknown instead of any, it's safer. To use the value of parent you will need to check the type before you can use it, see Type Guards.

[rs-amp]

Done, though I used the types that the content is normally traversed with.

[easen-amp]

This is just a comment regarding this entire method, I think its too complex (cyclomatic complexity - there's a lot of loops and if statements). Can this be simplied down into a series of functions, where each one can be unit tested.

[rs-amp]

Do you mean that the rewriteDependancy method is complex, or that the importTree method is complex? For the latter, it's probably refactoring it in another PR.

[easen-amp]

Can this function return lines, circularLinks & evalThis to make it clearer that this function manipulates these args.

Perhaps rename the function as technically it doesn't print anything.

[rs-amp]

evalThis is copied for each recursive call to this method. For the rest of the state, I've made a small class to hold it, and the method is now called addDependency.

[easen-amp]

Maybe change the circularLinks to be an arrary of an object, as it's not clear what each number represents.

[rs-amp]

Each number is an index in the lines of the tree. Neither of the numbers have any special meaning - they mean the same thing - it's just a pair of two linked indices. I think giving them names like index1, index2 might not be great.

[easen-amp]

type CircularLinkFrom = number;
type CircularLinkTo = number;
type CircularLink = [CircularLinkFrom, CircularLinkTo];