port-forward events should indicate user-defined forwards

### Expected behavior

Running the `jib-sync` example, which includes a user-defined port-forward, should be visible from within Cloud Code.
```yaml
portForward:
- resourceType: pod
resourceName: test-file-sync
port: 8080
```

### Actual behavior

The forward is not shown:

The `portEvent` provides no indication that the port-forward was user-defined:
```
{
"result": {
"timestamp": "2022-02-04T21:54:24.624180Z",
"portEvent": {
"id": "",
"task_id": "PortForward-1",
"localPort": 8080,
"podName": "",
"containerName": "",
"namespace": "default",
"portName": "",
"resourceType": "pod",
"resourceName": "test-file-sync",
"address": "127.0.0.1",
"targetPort": {
"type": 0,
"intVal": 8080,
"strVal": ""
}
}
}
}
```

### Information

- Skaffold version: 1.35.1
- Operating system: macOS
- Installed via: Cloud Code

Run the jib-sync example and inspect the portEvent produced for the user-defined port-forward in the shown configuration. Trace how that event is formed and consumed by Cloud Code. Done means the event indicates that the forward is user-defined so Cloud Code can display it.

Written by the indexing model from the issue text.