add deprecation notice

[SirSpidey]

Description

The code in the module is not officially supported by any team.

The following OCP VPC cluster modules are fully supported: terraform-ibm-base-ocp-vpc and terraform-ibm-ocp-all-inclusive

There are issues in the backlog to add fully supported modules that support deploying Vanilla IKS classic, Vanilla IKS VPC, and OCP Classic (non-vpc) modules, but there is no planned date for them.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

• When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
• Merge by using "Squash and merge".

[ocofaigh]

@SirSpidey We may need to revisit the wording here. I don't think we will archive the repo. The community seem to be adding PRs (such as this one today #88). As long as its clear its not supported by the core team, we should be fine

[SirSpidey]

@ocofaigh Changed the language and added a badge that we talked about internally.

We should add community-supported to the list of topics for the repo. I didn't do that yet (repo doesn't use the standard workflow).

[ocofaigh]

I think maybe leave out this line for now