docs: add containerized frontend development option

[slashpai]

Add Dockerfile.frontend-dev and update README with containerized development option that doesn't require Node.js on the host.

Description

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 UI/UX improvement
• ♻️ Code refactoring (no functional changes)
• ⚡ Performance improvement
• 🧪 Test updates

Related Issues

Fixes #

Changes Made

• Add Dockerfile.frontend-dev for running plugin dev server in container
• Update README with Option A (Podman) and Option B (Node.js) for frontend setup
• Document non-yarn alternative for start-console using npm_package_consolePlugin_name
• Restructure Setup Frontend section for clarity

Testing Done

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Tested on different browsers/devices (if applicable)

Test Details:

Screenshots/Videos

Click to expand

Definition of Done (DOD)

Code Quality

• Code follows project style guidelines and conventions
• Code has been self-reviewed for logic, readability, and best practices
• No debugging code (console.logs, commented code, etc.) left behind
• No linter errors or warnings introduced
• Code is properly commented where necessary

Testing

• Unit tests added/updated and passing
• Integration tests added/updated (if applicable)
• Manual testing completed successfully
• Edge cases and error scenarios tested
• No existing tests broken by changes

Documentation

• Code documentation updated (JSDoc, inline comments)
• README updated (if applicable)
• User-facing documentation updated (if applicable)
• CHANGELOG updated (if maintained)

Review & Quality

• PR description is clear and complete
• All related issues are linked
• Breaking changes are clearly documented
• Security implications considered and addressed
• Performance impact assessed
• Accessibility requirements met (if UI changes)

Pre-Merge

• All CI/CD checks passing
• At least one approval from code owner/reviewer
• All review comments addressed or resolved
• Branch is up to date with target branch
• No merge conflicts

Additional Notes

Reviewer Guidance

---

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: slashpai
Once this PR has been reviewed and has the lgtm label, please assign jhadvig for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@slashpai: 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.

[slashpai]

@diwanshi /@jhadvig Could you please take a look?