fix: Track graphs of item dependencies to find dependency cycles

[jfecher]

Description

Problem*

Resolves #1122

Summary*

Adds a dependency graph to catch cases where structs will cyclically depend on one other.

For example, the program:

struct Foo {
    bar: Bar,
}

struct Bar {
    foo: Foo,
}

Will now give the following error:

error: Dependency cycle found
  ┌─ /home/user/Code/Noir/noir/short/src/main.nr:6:1
  │  
6 │ ╭ struct Bar {
7 │ │     foo: Foo,
8 │ │ }
  │ ╰─' 'Bar' recursively depends on itself: Bar -> Foo -> Bar
  │  

The error is still issued if these are split across separate modules.

Additional Context

Note that self-referential structs like struct Foo { foo: Foo } are not currently caught - we may need a separate check for this.

This error is also only currently possible for cyclic struct dependencies, but once this is merged I'm going to expand this to more PRs to allow for globals and type aliases as well. This would implement #1734 as well as a similar feature to allow type aliases to reference other type aliases which is currently disallowed.

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[kevaundray]

Can you open up an issue for self referential structs?

[jfecher]

@kevaundray there is already #3490

[kevaundray]

Generally looks okay