Mark profiled job timing scope

[yoshifuminakamura]

Summary

• mark collected run timing as job-scoped in Result JSON
• record when a job includes profiler output
• keep profiled-job-only timing out of regular/profiled overhead pairing
• show profiled-job-only timing counts in Portal Usage
• update tests and the Result JSON contract notes

Validation

• bash -n scripts/result.sh scripts/tests/test_result_profile_data.sh scripts/tests/test_result_common_json_contract.sh scripts/tests/test_process_and_send_results.sh
• shellcheck -S error scripts/result.sh scripts/tests/test_result_profile_data.sh scripts/tests/test_result_common_json_contract.sh scripts/tests/test_process_and_send_results.sh
• bash scripts/tests/test_result_profile_data.sh
• bash scripts/tests/test_result_common_json_contract.sh
• bash scripts/tests/test_process_and_send_results.sh
• .venv/bin/python -m pytest result_server/tests/test_performance_telemetry.py
• .venv/bin/python -m pytest result_server/tests/test_portal_list_templates.py result_server/tests/test_usage_route.py result_server/tests/test_profile_usage_overview.py
• .venv/bin/python result_server/tests/run_result_server_tests.py