Archive the odh-manifests repo after v2.x odh-operator fully supports pulling component manifests from the component repositories

[LaVLaS]

Now that odh-operator v2.x can support pulling component manifests directly from the component repos (opendatahub-io/opendatahub-operator/issues/338) for developer testing AND building the local manifest for releases, the requirement to maintain a dedicated odh-manifests repo is no longer required. Once the CI/CD process for odh-operator is 100% operational with remote manifests, we can archive the odh-manifests repo as it will no longer be updated