update documentation to reflect connectionRef and mutualTLSSecretRef changes in #136 (#154)

<!--- Note to EXTERNAL Contributors -->
<!-- Thanks for opening a PR! 
If it is a significant code change, please **make sure there is an open
issue** for this.
We work best with you when we have accepted the idea first before you
code. -->

<!--- For ALL Contributors 👇 -->

## What was changed
updated documentation to reflect connectionRef and mutualTLSSecretRef
changes in #136

## Why?
The current documentation is outdated

Author: wadhah101

docs/concepts.md

@@ -87,7 +87,7 @@ Gradually increases the percentage of new workflow executions routed to the new
 
 ### Worker Options
 Configuration that tells the controller how to connect to the same Temporal cluster and namespace that the worker is connected to:
-- **connection**: Reference to a `TemporalConnection` custom resource
+- **connectionRef**: A reference to a `TemporalConnection` custom resource. This object contains a `name` field to specify the `TemporalConnection` resource.
 - **temporalNamespace**: The Temporal namespace to connect to
 - **deploymentName**: The logical deployment name in Temporal (auto-generated if not specified)
 

docs/configuration.md

@@ -149,7 +149,8 @@ Configure how workers connect to Temporal:
 
 ```yaml
 workerOptions:
-  connection: production-temporal     # Reference to TemporalConnection
+  connectionRef:
+    name: production-temporal     # Reference to TemporalConnection
   temporalNamespace: production      # Temporal namespace
   taskQueues:                        # Optional: explicit task queue list
     - order-processing
@@ -167,7 +168,8 @@ metadata:
   name: production-temporal
 spec:
   hostPort: "production.abc123.tmprl.cloud:7233"
-  mutualTLSSecret: temporal-cloud-mtls  # Optional: for mTLS
+  mutualTLSSecretRef: 
+    name: temporal-cloud-mtls  # Optional: for mTLS
 ```
 
 ## Gate Configuration
@@ -198,7 +200,8 @@ metadata:
 spec:
   replicas: 5
   workerOptions:
-    connection: production-temporal
+    connectionRef:
+      name: production-temporal
     temporalNamespace: production
   rollout:
     strategy: Progressive
@@ -226,7 +229,8 @@ metadata:
 spec:
   replicas: 2
   workerOptions:
-    connection: staging-temporal
+    connectionRef:
+      name: staging-temporal
     temporalNamespace: staging
   rollout:
     strategy: Progressive
@@ -246,7 +250,8 @@ Configure workers that handle multiple task queues:
 
 ```yaml
 workerOptions:
-  connection: production-temporal
+  connectionRef:
+    name: production-temporal
   temporalNamespace: production
   taskQueues:
     - order-processing

docs/migration-guide.md

@@ -92,7 +92,8 @@ metadata:
 spec:
   replicas: 3
   workerOptions:
-    connection: production-temporal
+    connectionRef:
+      name: production-temporal
     temporalNamespace: production
   rollout:
     strategy: Progressive  # Gradual rollout of new versions
@@ -190,7 +191,8 @@ metadata:
   namespace: default
 spec:
   hostPort: "production.abc123.tmprl.cloud:7233"
-  mutualTLSSecret: temporal-cloud-mtls  # If using mTLS
+  mutualTLSSecretRef: 
+    name: temporal-cloud-mtls  # Optional: for mTLS
 ---
 apiVersion: temporal.io/v1alpha1
 kind: TemporalConnection
@@ -199,7 +201,8 @@ metadata:
   namespace: default
 spec:
   hostPort: "staging.abc123.tmprl.cloud:7233"
-  mutualTLSSecret: temporal-cloud-mtls
+  mutualTLSSecretRef: 
+    name: temporal-cloud-mtls
 ```
 
 ### Step 3: Prepare Your Worker Code
@@ -267,7 +270,8 @@ metadata:
 spec:
   replicas: 3
   workerOptions:
-    connection: production-temporal
+    connectionRef:
+      name: production-temporal
     temporalNamespace: production
   # Start with Progressive strategy using conservative ramp percentages
   rollout:
@@ -674,4 +678,4 @@ See the [Concepts](concepts.md) document for detailed explanations of the resour
 
 This approach ensures a safe transition from unversioned to versioned workflows without disrupting running workflows or introducing deployment risks.
 
-The Temporal Worker Controller should significantly improve your deployment safety and reduce the risk of workflow disruptions while providing automated rollout capabilities that weren't possible with unversioned workflows. 
+The Temporal Worker Controller should significantly improve your deployment safety and reduce the risk of workflow disruptions while providing automated rollout capabilities that weren't possible with unversioned workflows.