[Doc]--Add labels to function statefulsets and services (apache#7428)

### Motivation

Pulsar release 2.4.0 supports Adding labels to function statefulsets and services. The code is implemented but the doc is not updated accordingly. 

Here is the code update PR: apache#4038

Therefore, i make this PR to update docs for releases:
master/2.5.2/2.5.1/2.5.0/2.4.2/2.4.1/2.4.0

### Modifications

Add a note in the doc "Setup: Configure Functions runtime" under the Pulsar Functions section

site2/docs/functions-runtime.md

@@ -10,6 +10,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.

site2/website/versioned_docs/version-2.4.0/functions-runtime.md

@@ -12,6 +12,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 ## Configure thread runtime
 It is easy to configure *Thread* runtime. In most cases, you do not need to configure anything. You can customize the thread group name with the following settings:
 

site2/website/versioned_docs/version-2.4.1/functions-runtime.md

@@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the  Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:   
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.   
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.

site2/website/versioned_docs/version-2.4.2/functions-runtime.md

@@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:   
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.   
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.

site2/website/versioned_docs/version-2.5.0/functions-runtime.md

@@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.

site2/website/versioned_docs/version-2.5.1/functions-runtime.md

@@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.

site2/website/versioned_docs/version-2.5.2/functions-runtime.md

@@ -11,6 +11,9 @@ Pulsar Functions support the following methods to run functions.
 - *Process*: Invoke functions in processes forked by Functions Worker.
 - *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
 
+#### Note
+> Pulsar supports adding labels to the Kubernetes StatefulSets and services while launching functions, which facilitates selecting the target Kubernetes objects.
+
 The differences of the thread and process modes are:
 - Thread mode: when a function runs in thread mode, it runs on the same Java virtual machine (JVM) with Functions worker.
 - Process mode: when a function runs in process mode, it runs on the same machine that Functions worker runs.