Use profile scopes for portal trigger variables

[yoshifuminakamura]

Summary

• Fill empty Portal submit filters from the resolved execution profile scopes
• Keep Profile Exp as Portal-only matching metadata and omit it from GitLab CI variables
• Add dry-run and submit coverage for Profile ID-only requests

Root cause / impact

The dev request did not fire because it was stored as submit_blocked with confirm_submit missing. While checking that path, Profile ID-only requests were also recording empty code/system values, which would make a confirmed trigger broader than the selected profile implied.

Validation

• /home/nakamura/fugakunext/venv/bin/python -m py_compile result_server/routes/admin.py
• /home/nakamura/fugakunext/venv/bin/python -m pytest result_server/tests/test_execution_profiles.py
• /home/nakamura/fugakunext/venv/bin/python -m pytest result_server/tests/test_execution_profiles.py result_server/tests/test_result_metadata_index.py result_server/tests/test_api_routes.py result_server/tests/test_app_dev_security.py result_server/tests/test_preflight.py
• /home/nakamura/fugakunext/venv/bin/python result_server/tests/run_result_server_tests.py