job metadata: function name, backend, timing information

[johannesgreiner]

What is the expected enhancement?

From users' perspective, it'd be great if jobs can return metadata such as

• which Function was run
• start & end times
• which backend was it run on (if possible)
  • n.b. current Functions only accept one backend as input

atm as a user, I need to manually keep track of which job id corresponds to which Function workload

[robertodr]

A suggestion for additional metadata:

• How much time was spent in the classical pre-/post-processing, if any.
• Hardware specifications for the classical compute used (number and model of vCPUs and RAM suffices, I believe)