Repository: PrefectHQ/prefect

Issue:
Improve docs surrounding "Cloud" tasks in the library
## Current behavior
*Please describe how the feature works today*

As it stands today, docs surrounding our "Cloud" tasks in the library are a bit contradictory, sometimes specifying that they rely on Cloud, sometimes saying they can be used with Cloud or Server. Additionally, they're filed under the "Cloud" category.

## Proposed behavior
*Please describe your proposed change to the current behavior*

At a minimum, it's worth cleaning up the docs to help users use the `FlowRunTask`. It's probably also worth renaming the Cloud category of tasks in the library-- maybe "orchestration" or "Prefect orchestration?" 


## Example
*Please give an example of how the enhancement would be useful*

Improving the docs would remove ambiguity surrounding the use of this task.


Discussion:

Resolving patch:
diff --git a/src/prefect/tasks/prefect/flow_run.py b/src/prefect/tasks/prefect/flow_run.py
--- a/src/prefect/tasks/prefect/flow_run.py
+++ b/src/prefect/tasks/prefect/flow_run.py
@@ -1,5 +1,4 @@
 from typing import Any
-from urllib.parse import urlparse
 
 from prefect import config, Task
 from prefect.client import Client
@@ -14,8 +13,9 @@ class FlowRunTask(Task):
 
     Args:
         - flow_name (str, optional): the name of the flow to schedule; this value may also be provided at run time
-        - project_name (str, optional): the Cloud project in which the flow is located; this value may also be provided
-            at run time
+        - project_name (str, optional): if running with Cloud as a backend, this is the project in which the flow is
+            located; this value may also be provided at runtime. If running with Prefect Core's server as the backend,
+            this should not be provided.
         - parameters (dict, optional): the parameters to pass to the flow run being scheduled; this value may also
             be provided at run time
         - **kwargs (dict, optional): additional keyword arguments to pass to the Task constructor
@@ -44,7 +44,8 @@ def run(
             - flow_name (str, optional): the name of the flow to schedule; if not provided, this method will
                 use the flow name provided at initialization
             - project_name (str, optional): the Cloud project in which the flow is located; if not provided, this method
-                will use the project provided at initialization
+                will use the project provided at initialization. If running with Prefect Core's server as the backend,
+                this should not be provided.
             - parameters (dict, optional): the parameters to pass to the flow run being scheduled; if not provided,
                 this method will use the parameters provided at initialization
 
@@ -52,20 +53,21 @@ def run(
             - str: the ID of the newly-scheduled flow run
 
         Raises:
-            - ValueError: if flow or project names were not provided, or if the flow provided cannot be found
+            - ValueError: if flow was not provided, cannot be found, or if a project name was not provided while using
+                Cloud as a backend
 
         Example:
             ```python
             from prefect.tasks.prefect.flow_run import FlowRunTask
 
-            kickoff_task = FlowRunTask(project_name="My Cloud Project", flow_name="My Cloud Flow")
+            kickoff_task = FlowRunTask(project_name="My Project", flow_name="My Cloud Flow")
             ```
 
         """
-        # verify that flow and project names were passed in some capacity or another
+        # verify that flow and project names were passed where necessary
         if flow_name is None:
             raise ValueError("Must provide a flow name.")
-        if project_name is None and "prefect.io" in urlparse(config.cloud.api).netloc:
+        if project_name is None and config.backend == "cloud":
             raise ValueError("Must provide a project name.")
 
         where_clause = {


Test patch: