Update Support Repos (#1351)

* update url for support package

* removed as repo doesnt exists

* update support repo location

* change repo location

* update org for repo

Author: ThatAmatoGuy

_docs/installation/runner/install-codefresh-runner.md

@@ -399,7 +399,7 @@ If your builds are stuck in Pending or failing with `Failed to validate connecti
 ### For Codefresh Runner installed with legacy CLI
 
 1. Delete `codefresh-certs-server` k8s secret;
-2. Download [`./configure-dind-certs.sh` script](https://github.com/codefresh-support/cf-utils/blob/master/configure-dind-certs.sh) and run it:
+2. Download [`./configure-dind-certs.sh` script](https://github.com/codefresh-io/cf-utils/blob/master/configure-dind-certs.sh) and run it:
 
 ```shell
 # Ensure the following environment variables are defined before running the command:

_docs/kb/articles/speed-builds-intermediate-images.md

@@ -20,4 +20,4 @@ Build not starting, showing only `Validating connection to Docker daemon` in `In
 1. Stop the build and restart it.
 2. [Check for outages here.](https://status.codefresh.io)
 3. If using an on-premise Codefresh instance or a Codefresh hybrid runner on your cluster, please check their status.
-4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include [a set of runner cluster logs](https://github.com/codefresh-support/hybrid-runner-support).
+4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include [a set of runner cluster logs](https://github.com/codefresh-io/codefresh-support-package).

_docs/kb/articles/stuck-in-validating-docker-daemon.md

@@ -58,7 +58,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile
 1. **Engine and DIND logs** for the failed build:
    - While the build is running, navigate to the cluster, and locate the pods named `engine-[buildID]` and `dind-[buildID]`.
    - Save those logs to a file and attach them to the ticket.
-   - Alternatively, you can use the [Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"} to collect the required data *while the affected build is running and the error message is received*.
+   - Alternatively, you can use the [Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"} to collect the required data *while the affected build is running and the error message is received*.
 1. **Helm values file** (to identify overrides such as images or other configurations).
 
 #### UI: Slowness and other issues
@@ -84,7 +84,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile
 1. **Ebs-csi pod logs** in the `kube-system` namespace if there are volume issues and you're using `ebs-csi`.
 1. Overview of cluster **scale up/down events** for the relevant timeframe.
 
-> Alternatively, to collect the data for 3 through 6, use the [Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"}.
+> Alternatively, to collect the data for 3 through 6, use the [Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"}.
 
 #### Security concerns