[chore] Fix 404 deadlinks for Cloudfoundry buildpack due to docs moving (#6283)

Author: jvoravong

deployments/cloudfoundry/buildpack/README.md

@@ -1,11 +1,11 @@
 # Splunk OpenTelemetry Collector Pivotal Cloud Foundry (PCF) Buildpack
 
-A [Cloud Foundry buildpack](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/2.11/tas-for-vms/toc-buildpacks-index.html) to install
+A [Cloud Foundry buildpack](https://docs.cloudfoundry.org/adminguide/buildpacks.html) to install
 the Splunk OpenTelemetry Collector for use with PCF apps.
 
 The buildpack's default functionality, as described in this document, is to deploy the OpenTelemetry Collector
 as a sidecar for the given app that's being deployed. The Collector is able to observe the app as a 
-[nozzle](https://docs.vmware.com/en/VMware-Tanzu-Operations-Manager/3.0/tile-dev-guide/nozzle.html) to
+[nozzle](https://docs.cloudfoundry.org/loggregator/nozzle-tutorial.html) to
 the [Loggregator Firehose](https://docs.cloudfoundry.org/loggregator/architecture.html).
 The Loggregator Firehose is one of the architectures Cloud Foundry
 uses to emit logs and metrics. This means that the Splunk OpenTelemetry Collector will be observing all