Show portal trigger run causes

[yoshifuminakamura]

Summary

• show Portal trigger causes in result tables and result details
• record trigger metadata in Result JSON and fall back to submitted trigger runs by pipeline id during rollout
• add admin trigger run history and repo/ref observations
• reduce routine trigger-run DB churn and avoid updating unchanged observations every timer tick

Validation

• /home/nakamura/fugakunext/venv/bin/python result_server/tests/run_result_server_tests.py -q
• /home/nakamura/fugakunext/venv/bin/python -m pytest result_server/tests/test_execution_profiles.py result_server/tests/test_trigger_display.py result_server/tests/test_results_loader.py
• shellcheck -S error scripts/result.sh scripts/tests/test_result_profile_data.sh scripts/tests/test_process_and_send_results.sh
• dev2 DB migration to schema v8
• dev2 trigger runner routine check: trigger_runs unchanged and trigger_observations unchanged
• dev2 service restarted and active