Add _repr_html_ for TaskGraph

[SimonHeybrock]

No description provided.

[jokasimr]

What should the html representation for Pipeline display?

Some suggestions:

• List of the providers in alphabetical order.
  • Show their descriptions (shortened if too long to fit, allow expansion / link to docs?).
  • For each provider, indicate if its preconditions are satisfied, perhaps display what is missing?
• List of parameters and their values + description / link to docs.

[SimonHeybrock]

List of the providers in alphabetical order.

We should order alphabetically by the type that is provided, the provider names may be of secondary interest.

There is also a third case, parameter tables. So a good starting point may be:

• Table with 3 columns
• First column: Type
• Second column: category (provider/param/param table)
• Third column: provider name/param value/summary of param table, depending on what we have in second column

Instead of a table with the category in the second column, one could also choose to output in three sections, each with 2 columns (1 and 3 above).

I think the main work will be to implement gathering all the info, we can then try different options for representing it?

[SimonHeybrock]

or each provider, indicate if its preconditions are satisfied, perhaps display what is missing?

Yes, we could list all the dependencies, may indicate with color if it is satisfied?

[jokasimr]

I think the main work will be to implement gathering all the info

Currently Pipeline stores parameters as provider functions without arguments.
Therefore we can not directly determine if the pipeline was initiated with a provider function without arguments or if it was initiated with a parameter.

We could use some heuristics.
Would it be correct to display every zero-arguments provider as a parameter?
It would make sense if the provider functions are pure, but I don't know if that is a guarantee or just a recommendation from sciline to make the providers pure.

Another stricter option would be to treat every zero-arguments anonymous function as a parameter.

A third option would be to explicitly store information about what types were provided as parameters and what types were provided as functions.

[SimonHeybrock]

We could use some heuristics.

We can use the same approach as in the graph visualization code, no tricks or heuristics required (maybe going via a string can be avoided as well):

sciline/src/sciline/visualize.py

Lines 110 to 114 in f04f65e

	# Do not draw dummy providers created by Pipeline when setting instances
	if p_name in (
	f'{_qualname(Pipeline.__setitem__)}.<locals>.<lambda>',
	f'{_qualname(Pipeline.set_param_table)}.<locals>.<lambda>',
	):

[SimonHeybrock]

Reopening since only Pipeline._repr_html_ has been implemented so far.