nullify the base config in the applicable examples (#18)

**Description** <Describe what changed.>
This PR nullifies the baseConfig in the applicable examples. The current
example falsely shows an empty object for the `baseConfig`, which is
incorrect when we want to nullify them.

**Testing** <Describe how you tested the change.>
Tested locally3

**Documentation** <Describe any documentation that was added.>
N/A

charts/orchestrator/Chart.yaml

@@ -20,7 +20,7 @@ type: application
 # This is the chart version. This version number should be incremented each time we
 # make changes to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.5
+version: 0.1.6
 
 # This is the version number of the application being deployed. This version number
 # should be incremented each time we make changes to the application. Versions are

charts/orchestrator/example-values/minimal-orchestrator-standalone.yaml

@@ -3,7 +3,7 @@ replicaCount: 1
 orchestrator:
   # We explicitly set the baseConfig to empty, so that the baseConfig will not be 
   # used.
-  baseConfig: {}
+  baseConfig: null
   customConfig:
     version: 0.0.1