[RHCLOUD-47206] Create V1 to V2 Concept Mapping Reference

[Ellen-Yi-Dong]

Related JIRA ticket: https://redhat.atlassian.net/browse/RHCLOUD-47206

Acceptance Criteria listed in ticket:

• Create a Markdown table mapping each V1 concept to its V2 equivalent (e.g., "Default Access" → Default Workspace role binding, "Access Group" → Workspace, "Resource Definition" → Resource Type + KSL schema)
• Include a brief explanation of why the mapping isn't 1:1 where applicable
• Cover permission evaluation differences (flat list vs. hierarchical traversal)
• Cross-reference with RHCLOUD-47172: Write the "Design Permissions Schema" how-to guide
• Refinement and RHCLOUD-47173: Write the "Migrate Existing Applications to RBAC" how-to guide
• Release Pending
• Cross-reference the existing migrate-from-rbac-v1-to-v2.mdx page

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: project-kessel/docs/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: fcb3ff04-9950-43a0-81b2-21bd15f2850d

---

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