feat: API pipeline run get has execution summary

[yuechao-qin]

TL;DR

Added execution statistics to the pipeline run get endpoint (GET /api/pipeline_runs/{id}).

What changed?

• Enhanced the get method to optionally include execution statistics
• Added a new parameter include_execution_stats (default: False) to the get method
• Extracted the execution stats population logic into a new helper method _populate_execution_stats

How to test?

1. Call the pipeline run get endpoint with include_execution_stats=True
2. Verify that the response includes execution status statistics and summary
3. Run the new tests in TestPipelineRunServiceGet class to ensure the functionality works as expected

Run the new test cases in tests/test_api_server_sql.py:

pytest tests/test_api_server_sql.py

Why make this change?

• Related to API Server - Add has_ended to the response of PieplineRunsService.list #87
• tangle-deploy needs to know if a specific pipeline run is completed

[yuechao-qin]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: GetExecutionNodes API returns number of total and ended nodes #99
• test: Add tests for GetGraphExecution API #98
• feat: API pipeline run get has execution summary #97 👈 (View in Graphite)
• feat: API pipeline run list has execution summary #96
• refactor: Function to get execution status stats #95
• feat: Model to track node states and has_ended flag #94
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.