Add Hasura relationships to support Expansion Runs UI

[jeffpamer]

Required for NASA-AMMOS/aerie-ui#577

• Review: By commit
• Merge strategy: Merge (no squash)

Description

Adds the following object/array relationships:

• expanded_sequences . ( seq_id, simulation_dataset_id ) → sequence . ( seq_id, simulation_dataset_id )
• expanded_sequences . expansion_run_id → expansion_run . id

Allowing the UI to gather the necessary details to display information about the expanded sequences and the applicable activity types within each expansion/sequence.

Verification

Upon rebuilding, confirmed the following query ran successfully in the Hasura API Explorer

{
  expansionRuns: expansion_run(order_by: {id: desc}) {
    created_at
    expansion_set {
      command_dict_id
      created_at
      id
      name
    }
    expanded_sequences {
      edsl_string
      expanded_sequence
      id
      seq_id
      sequence {
        activity_instance_joins {
          simulated_activity {
            id
            activity_type_name
          }
        }
      }
    }
    simulation_dataset {
      dataset_id
      simulation {
        plan {
          id
          name
        }
      }
    }
    id
  }
}

Documentation

N/A

Future work

N/A

[Mythicaeda]

Tested it and it LGTM!

[jeffpamer]

I'm assuming the e2e test is failing due to intermittent failures unrelated to this change? But please let me know if I'm likely wrong in that assumption and I'll check back in the morning!

[cohansen]

Looks good to me! I see the e2e tests are passing now, did they fail on an earlier run?

[jeffpamer]

Looks good to me! I see the e2e tests are passing now, did they fail on an earlier run?

Yeah it looks like the first two attempts failed, but third time was the charm. Thank you for the review!