[NO-JIRA]: Add plugins doc section on Console version compatibility

[vojtechszocs]

Summary by CodeRabbit

• Documentation
  • Added Console version compatibility guidance for dynamic plugins, covering strategies for managing single and multiple Console versions per code branch with pros, cons, and implementation examples.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vojtechszocs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [vojtechszocs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8efe80a2-fc35-4c8f-a48e-65b57a7633d0

📥 Commits

Reviewing files that changed from the base of the PR and between 21101de and 3d8213c.

📒 Files selected for processing (1)

• frontend/packages/console-dynamic-plugin-sdk/README.md

---

📝 Walkthrough

Walkthrough

This change adds documentation to the Console dynamic plugin SDK README outlining version compatibility strategies for plugin developers. It introduces guidance for two approaches: maintaining separate code branches targeting specific Console versions, or supporting multiple Console versions within a single branch. The documentation includes examples, trade-offs, and recommendations for plugin SDK versioning and CI configurations. The content is duplicated across two locations within the README. No code modifications or behavioral changes are included.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding documentation about Console version compatibility strategies for dynamic plugins.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vojtechszocs]

@jseseCCS Hi, can you please review this docs change?

[logonoff]

/label px-approved

[vojtechszocs]

/retest

[openshift-ci]

@vojtechszocs: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.