docs: add deprecation notice of Repository CR PipelineRun status

- Add prominent deprecation notice in repositorycrd.md and statuses.md
- State the field will be removed in a future release
- Improves wording; no functional changes

Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

Author: zakisk

docs/content/docs/guide/repositorycrd.md

@@ -15,6 +15,10 @@ The Repository CR serves the following purposes:
 - Letting you declare [custom parameters]({{< relref "/docs/guide/customparams" >}})
   within the `PipelineRun` that can be expanded based on certain filters.
 
+{{< hint danger >}}
+The `pipelinerun_status` field in the `Repository` CR is scheduled for deprecation and will be removed in a future release. Please avoid relying on it.
+{{< /hint >}}
+
 To configure Pipelines-as-Code, a Repository CR must be created within the
 user's namespace, for example `project-repository`, where their CI will run.
 

docs/content/docs/guide/statuses.md

@@ -107,6 +107,10 @@ repository.
 The most recent five statuses of any PipelineRuns associated with a repository
 are stored within the corresponding repository custom resource (CR).
 
+{{< hint danger >}}
+The `pipelinerun_status` field in the `Repository` CR is scheduled for deprecation and will be removed in a future release. Please avoid relying on it.
+{{< /hint >}}
+
 ```console
 % kubectl get repo -n pipelines-as-code-ci
 NAME                  URL                                                        NAMESPACE             SUCCEEDED   REASON      STARTTIME   COMPLETIONTIME