Extend job report with an optional name property

[pgetta]

No description provided.

[GianlucaFicarelli]

For more context, in what cases is the name of the job going to be used?

[pgetta]

For more context, in what cases is the name of the job going to be used?

In the UI we want to show something to the user that would allow them to identify the cost source (in addition to type and subtype).

In theory, if we store somewhere the execution itself (which is not the case for many services), we can map jobId from accounting to those entities and have the name from there. Not sure what's best, please let me know your thoughts.

The current idea about the name value:

• for single cell model it's going to be the name of the model itself (because user can re-run simulation multiple times without saving anything - maybe this is actually something to address).
• for bigger simulations - user will define the name.
• for ML - there is a title of the chat that is automatically generated.