[grafana/agent] Format with prettier

Consistent formatting improves readability and makes it easier for tools to transform the source.

The general human understanding of Markdown has some ambiguities so it's possible this PR will break some documentation presentation because the formatter follows the CommonMark specification.

In this case, this PR specifically enables a follow up PR where links are automatically updated to follow the current guidance in Writers' Toolkit.
Consider adopting `prettier` in your local workflow and enforcing it in CI to help eliminate those ambiguities in the future.

Repository: grafana/agent
Created-By: migrator

docs/sources/flow/reference/components/discovery.file.md

@@ -40,7 +40,7 @@ The following arguments are supported:
 | `files`            | `list(string)` | Files to read and discover targets from. |         | yes      |
 | `refresh_interval` | `duration`     | How often to sync targets.               | "5m"    | no       |
 
-The last path segment of each element in `files` may contain a single _ that matches any character sequence, e.g. `my/path/tg\__.json`.
+The last path segment of each element in `files` may contain a single \_ that matches any character sequence, e.g. `my/path/tg\__.json`.
 
 ## Exported fields
 

docs/sources/operator/getting-started.md

@@ -41,8 +41,7 @@ You can find the set of Custom Resource Definitions for Grafana Agent Operator i
 To deploy the CRDs:
 
 1.  Clone the agent repo and then apply the CRDs from the root of the agent repository:
-    `     kubectl apply -f production/operator/crds
-    `
+    `    kubectl apply -f production/operator/crds`
 
         This step _must_ be completed before installing Agent Operator—it will