SVD feature selection exploration

Select the most informative attributes via SVD, given 2+ input attributes and at least 1 target. This endpoint is always asynchronous — it schedules a job and returns `202`; fetch the result from [Get job information](/docs/api-reference/jobs/jobs-jobid-get) using the `sym-job-id` response header. The request body is an **ExploreContext** object: `{"values": [<MLContext>, ...]}` — one `MLContext` entry per exploration to run in this call. Unlike VIF/SVD/PCA, this endpoint does **not** validate individual attribute names/indices before scheduling the job — an invalid attribute here is accepted at request time and only surfaces as a generic, unhelpful `500` at job-status time (see the `500` response below), not a clean `400`.

curl -X POST "https://example.com/c1/projects/nbra_prj_iris/exploresvdfs?useLocal=true" \  -H "Content-Type: application/json" \  -d '{    "values": [      {        "targets": [          "18"        ],        "inputAttributes": [          "0",          "1",          "2",          "3",          "4",          "5",          "6",          "7",          "8",          "9",          "10",          "11",          "12",          "13",          "14",          "15",          "16"        ],        "extraParameters": {}      }    ]  }'

{  "statusCode": 200,  "statusString": "Job is finished",  "values": {    "KSVSMap": {      "values": [        {          "0": "sepal_length",          "1": "sepal_width",          "2": "petal_length",          "3": "petal_width",          "4": "sepal_lengt_b1",          "6": "sepal_width_b1",          "8": "petal_length_b1",          "11": "petal_width_b2"        }      ]    }  }}

{  "statusCode": 202,  "statusString": "Job Created",  "values": {}}

{  "statusCode": 400,  "statusString": "Less than 1 target for svd",  "values": {}}

{  "statusCode": 500,  "statusString": "Error computing SVD, no values found",  "values": {}}