[TASK] Visualize the graph of components and resources

[j-bryan]

---

Issue Description

Is your feature request related to a problem? Please describe.
It can be difficult for a user to determine if their inputs match their intention. It would be helpful if there was a way to visually represent what the received input is so that users could more easily learn HERON and debug their inputs.

Describe the solution you'd like
At a minimum, this feature could output an image of a directed graph with nodes for components and resources and directed edges indicating production and consumption of resources. The NetworkX library could be used to this. This could be enhanced with additional information, such as node sizing by relative capacity of each component or information on the cash flows associated with each component. With more information, it may be beneficial to make this diagram interactive rather than a static image by using a library like plotly.

Describe alternatives you've considered
A simple adjacency matrix could be printed to the terminal. However, I believe this would be more difficult for new users to interpret.

---

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

• 1. Is it tagged with a type: defect or task?
• 2. Is it tagged with a priority: critical, normal or minor?
• 3. If it will impact requirements or requirements tests, is it tagged with requirements?
• 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

---

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

• 1. If the issue is a defect, is the defect fixed?
• 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?