docs: add new section on managing provisioners from the dashboard (#16563)

closes #16513 


[preview](https://coder.com/docs/@16513-manage-ext-provisioners/admin/provisioners/manage-provisioner-jobs)

---------

Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>

docs/admin/users/groups-roles.md

@@ -24,7 +24,7 @@ Roles determine which actions users can take within the platform.
 | Manage **ALL** Templates                                        |         |            | ✅              | ✅     |
 | View **ALL** Workspaces                                         |         |            | ✅              | ✅     |
 | Update and delete **ALL** Workspaces                            |         |            |                | ✅     |
-| Run [external provisioners](../provisioners.md)                 |         |            | ✅              | ✅     |
+| Run [external provisioners](../provisioners/index.md)           |         |            | ✅              | ✅     |
 | Execute and use **ALL** Workspaces                              |         |            |                | ✅     |
 | View all user operation [Audit Logs](../security/audit-logs.md) | ✅       |            |                | ✅     |
 
@@ -80,7 +80,7 @@ Note that these permissions only apply to the scope of an
 A malicious Template Admin could write a template that executes commands on the
 host (or `coder server` container), which potentially escalates their privileges
 or shuts down the Coder server. To avoid this, run
-[external provisioners](../provisioners.md).
+[external provisioners](../provisioners/index.md).
 
 In low-trust environments, we do not recommend giving users direct access to
 edit templates. Instead, use

docs/admin/users/organizations.md

@@ -37,7 +37,7 @@ From there, you can manage the name, icon, description, users, and groups:
 
 Any additional organizations have unique admins, users, templates, provisioners,
 groups, and workspaces. Each organization must have at least one dedicated
-[provisioner](../provisioners.md) since the built-in provisioners only apply to
+[provisioner](../provisioners/index.md) since the built-in provisioners only apply to
 the default organization.
 
 You can configure [organization/role/group sync](./idp-sync.md) from your
@@ -71,7 +71,7 @@ Next deploy a provisioner and template for this organization.
 
 ### 2. Deploy a provisioner
 
-[Provisioners](../provisioners.md) are organization-scoped and are responsible
+[Provisioners](../provisioners/index.md) are organization-scoped and are responsible
 for executing Terraform/OpenTofu to provision the infrastructure for workspaces
 and testing templates. Before creating templates, we must deploy at least one
 provisioner as the built-in provisioners are scoped to the default organization.
@@ -90,7 +90,7 @@ provisioner as the built-in provisioners are scoped to the default organization.
 
    In this example, start the provisioner using the Coder CLI on a host with
    Docker. For instructions on using other platforms like Kubernetes, see our
-   [provisioner documentation](../provisioners.md).
+   [provisioner documentation](../provisioners/index.md).
 
    ```sh
    export CODER_URL=https://<your-coder-url>