evaluation done, stop development and archive related repositories

[henrjk]

ods-pipeline has been used in internal projects with success. It allowed us to build and deploy software with flexibility and efficiency while at the same time building and polishing ods-pipeline with a focus on quality.

Based on this experience, ods-pipeline is a viable alternative to a Jenkins based CI/CD system.
However, Tekton Pipelines is still under active development. Features such as Step Reusability proposed in TEP-0142 will make using it more attractive. However these feature had not been available with the tektoncd/pipeline version which ods-pipeline was built for. Currently, they are in beta in OpenShift Pipelines version 1.16 (tektoncd/pipeline v0.62.x LTS).

Once Tekton features have settled and stabilized sufficiently for our purposes, we may reevaluate its usefulness. However we would also want to ensure that Tekton pipelines are broadly adopted. Ideally, instead of building our own CI/CD pipeline system based on Tekton or some other technology, it would be better to contribute upstream and/or integrate needed capabilities into that tech in a lightweight, composable fashion.

That said, for the foreseeable future, we have no plans to further evaluate and/or maintain ods-pipeline.

To signal this to anyone coming across the ods-pipeline and related ods-pipeline-* repositories let's do the following:

In all repositories:

1. In About add a topic 'archived'
2. Add to repo description a postfix saying Archived: See this issue
3. Use the github Archive feature. This makes each repo read-only and closes all issues which cannot be reopened. However the repos can still be forked and if needed unarchived.

In addition in the main repo ods-pipeline repo also add a section to README.md

1. Add a "Status: Archived" section in ods-pipeline repository READMEs linking to this issue.

The mentioned readme section should summarize this text. The draft for that is

## Status: Archived

**WARNING: At the moment we have no plans to further evaluate and/or maintain ods-pipeline. For more details, read [#748](https://github.com/opendevstack/ods-pipeline/issues/748).**

Let me know what you think!

I would like to thank everybody who helped build ods-pipeline and who dared to use it!
My big thanks to @michaelsauter for coming up with the idea, contributing and guiding us and for being awesome ✨ !