Minimal `PodResult` Model

[Synicix]

struct PodResult {
    annotation: Option<Annotation>,
    hash: String,
    pod_job: PodJob,
    assigned_name: String,
    state: RunState,
    created: u64,
    terminated: u64,
}

[guzman-raphael]

Summary from 11/23/24 - 11/27/24 meetings:

• PodResult: A historical record of a previous, completed PodJob run (i.e. PodRun) in either a "success" or "fail" state. Created by Orcapod's orchestrator.
• PodOutput: The actual computed output (i.e. generated files) produced from a completed "successful" PodRun. Created by Orcapod's orchestrator.
• A PodJob specification could have many PodResults (mix for "success" and "fail"), however, there exists a 1:1 association between:
  • PodOutput and the PodResult that produced it.
  • PodJob and a "successful" PodResult.
• PodResult model should have a reference to the corresponding output files as an Option<PodOutput>. This allows it to be easily indexed from a PodResult and convey that "failed" runs will have it set to None.
• PodResult model should include an attribute image_used: String which will indicate the actual, resolved (i.e. [server]/[org]/[user]@[sha256] digest) used during the run. (tracked in Capture image@digest on starting containers #9)

[guzman-raphael]

After discussions, we've decided to reclassify this issue as a minimal PodResult implementation (see updated description) and move other features discussed here into their own dedicated issues.