customRuntimeOptions in "Creates a new Pulsar Source in cluster mode" API call in source connector doesn't add nodeselectors & tolerations

**Describe the bug**
The API call "Creates a new Pulsar Source in cluster mode" [LINK](https://pulsar.apache.org/source-rest-api/#operation/SourcesBase_registerSource) Adding node selectors and toleration under customRuntimeOptions flag doesn't seem to add those selectors & toleration to the created pulsar functions source pods. For reference I'm using apache pulsar installed using helm on k8

**To Reproduce**
Steps to reproduce the behavior:
1. Create an "Creates a new Pulsar Source in cluster mode" with "customRuntimeOptions": json.dumps(
"nodeSelectorLabels": {
"customLabel": "value"
},
"tolerations": [
{
"key": "custom-key",
"value": "value",
"effect": "NoSchedule"
}
]) As mentioned [here](https://pulsar.apache.org/docs/3.1.x/functions-runtime-kubernetes/)

2, the created source connector doesn't have the node selector / toleration

**Expected behavior**
The passed nodeselectors and tolerations from customRuntimeOptions should be inherited onto the pods that get created

**Desktop (please complete the following information):**
- OS: Mac OS 13.5.2 (22G91) Apple M1 Pro

**Additional context**
Add any other context about the problem here.

Start with the “Creates a new Pulsar Source in cluster mode” API operation and the customRuntimeOptions handling in the Helm-deployed Kubernetes setup. Reproduce the issue, inspect the created Pulsar source connector pods, and compare their node selectors and tolerations with the submitted options. Done means both settings are inherited by the created pods.

Written by the indexing model from the issue text.