chore: move sast_fp_detection flow to v1

What does this merge request do and why?

Recently 1st stable version of Flow Registry has been released, as a result we try to move all existing flows to it

How to set up and validate locally

export DEFINITION="sast_fp_detection/v1"
export GOAL="667"
export PROJECT_ID="23"

curl -X POST \
    -H "Authorization: Bearer $GDK_API_TOKEN" \
    -H "Content-Type: application/json" \
    -d '{
        "project_id": "'$PROJECT_ID'",
        "agent_privileges": [1,2,3,4,5],
        "goal": "'$GOAL'",
        "start_workflow": true,
        "workflow_definition": "'$DEFINITION'",
        "environment": "web"
    }' \
    http://gdk.test:3000/api/v4/ai/duo_workflows/workflows

Merge request checklist

• Tests added for new functionality. If not, please raise an issue to follow up.
• Documentation added/updated, if needed.
• If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.