Creation of `multifunctional` processes and databases

[cmutel]

Feature request

The current way we create processes in the GUI needs to be tweaked. Instead of this:

We need to make the following changes:

• Change the label of New activity -> New process.
• Change the label of Duplicate activity to Duplicate node
• Change the label of Delete activity to Delete node

• The GUI panel for New process should be changed
  • The layout should be changed to a grid of labels / text input boxes
  • The title of this panel should be changed to New process
  • The fields should be "Process name", "Reference product name", "Unit" (default="kilogram", node data attribute "unit"), "Location" (default="GLO", node data attribute "location"), and these should be applied to the newly created "process" node.
• Creating a new process should also create a separate node of type product with the name of the "reference product" from the creation panel
  • The new product Node should take the "Reference product name" as "name", as well as "unit" and "location" attributes.
• Creating a new process should create a new exchange on the new process:

new_process_node.new_edge(
    input=new_product_node,
    type=bw2data.labels.production_edge_default,
    amount=1,
)

• A new action, New product, should be added to the contextual menu. This should pop up a menu

Users don't need to think about the Database type - this should be a reflection of the data in the database.

• If we have the same product referenced as both an input and an output, it can only be functional in one place, not both places
• The right inputs panel should have the column "functional"
• If a process is edited so that it has two functional edges (looking across both the inputs and outputs), then its type needs to change to multifunctional, and the database backend needs to change to multifunctional.
• If the database changes to "multifunctional", we need to pop up the default allocation box and make the user choose something (even if it has errors at first).
• If the database backend changes to multifunctional, the left panel listing the nodes needs to be refreshed.
• If a process is edited so that it has only one functional edge (looking across both the inputs and outputs), then its type needs to change to process.

[cmutel]

@zoltanszocs really great work so far, here are some refinements:

• Instead of just disallowing making the same product functional in more than one place (this works), we need to give some feedback. Otherwise the user just feels like the software is broken. Can we have a modal popup with "Products can only be functional in one edge.\nThis product is already functional in:\n{edge}" or something similar?
• Quick: When first creating a process, the creation of the product node and the edge from product node to process node works. However that edge should have "functional"=True.
• Quick: The popup window when a database becomes multifunctional is great. Can we customize the language or add in an optional flag which is shown only when this change first happens which adds language like: "This database now has a multifunctional process. In order to do calculations correctly, we need to define a default allocation for this database. Please choose from the following possibilities:"
• The popup window when a database becomes multifunctional is useless if we don't have any properties defined:

In this case, if there is no possible allocation strategy, we should instead show a modal popup with the message: "This database now has a multifunctional process. In order to do calculations correctly, we need to define a default allocation; however, there are no properties available for all products. Defaulting to equal allocation, please add product properties and then select a different allocation method."

• Quick: I can make the same product functional twice if both edges are in inputs. This should not be allowed. Sorry if this wasn't clear before.

[cmutel]

Some additional tasks taken from Slack:

• Any time someone clicks on a checkbox in the functional column (either on or off) regardless of activity node type, do the following:
  • Save the exchange
  • Call exchange.output.allocate()
  • Call exchange.output.save()
  • Refresh the activity input/output tables and the lower left hand database table
• Anytime a change is made to an exchange whose output type is multifunctional:
  • Save the exchange
  • Call exchange.output.allocate()
  • Call exchange.output.save() - This is needed to purge orphaned allocated processes who shouldn't exist anymore
  • Refresh the activity input/output tables and the lower left hand database table