Add conda envs or used containers to the bug report mails

[bgruening]

It would be nice if the bug report mails could include the path to the used conda env or the container used.

[bgruening]

@natefoo @gmauro what do you think? Anything else that we should add? The JWD maybe?

[hexylena]

anecdotally I don't think I ever really read the bug report mails, I just find the one link to their dataset info page and click on that, since the information is more complete and presented in a nicer fashion that. But can't hurt to stuff more info in there, especially for folks like @selten who use the feature heavily.

[natefoo]

👍, if it's available then sure, put it in the email, but I often click through to the dataset/job info page as @hexylena does.

One major problem is that only the dependency resolution is shown on that page currently, not the container resolution. Additionally, I am pretty sure that you're seeing the dependency as it resolves presently, not the dependency that was necessarily used when the job ran.

Job command line in addition to tool command line would also be helpful here. Often times I am going to the log for this (although just seeing the container that was used for the job would probably greatly reduce the need to see this).

[natefoo]

Related: #11109.

[mvdbeek]

Collection should run as job metric.

[natefoo]

That makes sense, yeah, especially considering remote resolution in Pulsar.