Add tip to name one task platform as default

Author: jvalkeal

spring-cloud-dataflow-docs/src/main/asciidoc/configuration-cloudfoundry.adoc

@@ -207,6 +207,8 @@ spring:
                   appNamePrefix: qa1
 ----
 
+TIP: By defining one platform as `default` allows you to skip using `platformName` where its use would otherwise be required.
+
 When launching a task, pass the value of the platform account name using the task launch option `--platformName`  If you do not pass a value for `platformName`, the value `default` will be used.
 
 NOTE: When deploying a task to multiple platforms, the configuration of the task needs to connect to the same database as the Data Flow Server.

spring-cloud-dataflow-docs/src/main/asciidoc/configuration-kubernetes.adoc

@@ -288,6 +288,9 @@ spring:
                 limits:
                   memory: 2048m
 ----
+
+TIP: By defining one platform as `default` allows you to skip using `platformName` where its use would otherwise be required.
+
 When launching a task, pass the value of the platform account name using the task launch option `--platformName`  If you do not pass a value for `platformName`, the value `default` will be used.
 
 NOTE: When deploying a task to multiple platforms, the configuration of the task needs to connect to the same database as the Data Flow Server.

spring-cloud-dataflow-docs/src/main/asciidoc/configuration-local.adoc

@@ -347,6 +347,8 @@ spring:
 
 ----
 
+TIP: By defining one platform as `default` allows you to skip using `platformName` where its use would otherwise be required.
+
 When launching a task, pass the value of the platform account name using the task launch option `--platformName`  If you do not pass a value for `platformName`, the value `default` will be used.
 
 NOTE: When deploying a task to multiple platforms, the configuration of the task needs to connect to the same database as the Data Flow Server.