Document the nuance of the auto-release flag

It means different things on the RP and RPA.

docs/modules/ROOT/pages/advanced-how-tos/releasing/create-release-plan-admission.adoc

@@ -25,6 +25,8 @@ When an application is ready for release, the Development team contacts the owne
 apiVersion: appstudio.redhat.com/v1alpha1
 kind: ReleasePlanAdmission
 metadata:
+ labels:
+   release.appstudio.openshift.io/auto-release: 'true' <.>
  name: sre-production <.>
  namespace: managed-workspace <.>
 spec:
@@ -40,6 +42,7 @@ spec:
 ----
 
 +
+<.> Optional: Control whether or not this ReleasePlanAdmission is entirely disabled. If set to false, attempted releases will fail with a validation error. Defaults to true.
 <.> The name of the release plan admission.
 <.> The Managed environment team's workspace.
 <.> A list of applications that you want to enable to be deployed in the managed workspace.

docs/modules/ROOT/pages/advanced-how-tos/releasing/create-release-plan.adoc

@@ -25,7 +25,7 @@ apiVersion: appstudio.redhat.com/v1alpha1
 kind: ReleasePlan
 metadata:
  labels:
-   release.appstudio.openshift.io/auto-release: 'true'
+   release.appstudio.openshift.io/auto-release: 'true' <.>
    release.appstudio.openshift.io/standing-attribution: 'true'
    release.appstudio.openshift.io/releasePlanAdmission: 'rpa-name' <.>
  name: sre-production <.>
@@ -39,6 +39,7 @@ spec:
 ----
 
 +
+<.> Optional: Control if Releases should be created automatically for this ReleasePlan when tests pass. Defaults to true.
 <.> Optional: The name of the RPA to use if more than one RPA references the specified application.
 <.> The name of the release plan.
 <.> The development team's workspace.