Separate usage guides between implementations

[thepetk]

Which area this feature is related to?

/area documentation

Which area is this documentation change is related to?

Doc files inside the repository

Issue details

We should separate the documentation (usage guides) inside the repository to 3 different implementations:

As seen in the diagram, in the main Readme.md file, in the usage section, we should link the three guides (Java, Go, JS) . In each usage guide we can include:

• Any building information needed (e.g for the CLIs)
• Usage information
• Output information

Target date: 3 Apr 2023

[openshift-ci]

@thepetk: The label(s) area/repository cannot be applied, because the repository doesn't have them.

In response to this:

Which area this feature is related to?

/area documentation

Which area is this documentation change is related to?

/area repository documentation

Issue details

We should separate the documentation (usage guides) inside the repository to 3 different implementations:

As seen in the diagram, in the main Readme.md file, in the usage section, we should link the three guides (Java, Go, JS) . In each usage guide we can include:

• Any building information needed (e.g for the CLIs)
• Usage information
• Output information

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jeffmaury]

The JS and Java implementations are to be removed they are not up to date

[thepetk]

@jeffmaury I've added deprecation warnings inside the docs in order to be clear to everyone that those implementations are not up-to-date, till we remove them completely.