Avoid duplicate profile attribution for triggered results

[yoshifuminakamura]

Summary

Tightens Profile Operations Overview result attribution and refreshes stale admin/mTLS docs.

Changes

• Attribute results with execution_trigger.id only to the matching trigger profile, or to the profile itself for manual-button results
• Keep scope fallback only for legacy/non-Portal results that do not carry an execution trigger id
• Add tests for avoiding duplicate profile attribution
• Update developer reference to include execution profile and GitLab trigger admin routes
• Update site onboarding docs and legacy BenchPark bridge checks to reflect mTLS client certificate/key requirements

Validation

• .venv/bin/python result_server/tests/run_result_server_tests.py
• .venv/bin/python result_server/tests/check_site_config.py
• shellcheck -S error benchpark-bridge/scripts/ci_generator.sh
• dev2 helper check confirmed latest manual result remains attributed to qws-fugaku with snapshot context