Planner doesn't fully leverage RM's provision result information

### 🐛 Describe the bug

`Provisioner.Provision()` returns `*ProvisionResult`

```
type ProvisionResult struct {
ProvisionID string
Provider string
Status ProvisionStatus
Region string
CreatedAt/UpdatedAt time.Time
// provider details
Kubernetes *KubernetesProvisionDetail
AWS *AWSProvisionDetail
LambdaCloud *LambdaCloudProvisionDetail
RunPod *RunPodProvisionDetail
}
```

```
type DefaultDecision struct {
ProvisionID string `json:"provision_id,omitempty"` // only provision_id
}
```

in this case, how can MDS launch tasks?

### Steps to Reproduce

N/A

### Expected behavior

it should provide all the details

### Environment

nightly

Start by tracing Provisioner.Provision() from its ProvisionResult return value into DefaultDecision and the MDS task-launch path. Compare the provider-specific details in ProvisionResult with what MDS receives; done means MDS can access the provisioning information required to launch tasks, with tests covering the result propagation.

Written by the indexing model from the issue text.