docs: document v2 owner resources for terraform provider

[OneWhoNests]

Summary

• Adds a new "Managing app, entitlement, and connector ownership" section covering the v2 owner resources (conductorone_app_owner_user/_entitlement, conductorone_app_entitlement_owner_user/_entitlement, conductorone_connector_owner_user/_entitlement), which assign a single owner per resource and support entitlement-type owners.
• Relabels the existing user_ids-based owner resources (conductorone_app_owner, conductorone_app_entitlement_owner) as legacy v1, with a note that conductorone_app_resource_owner has no v2 equivalent yet.
• Adds a v1 vs v2 comparison table and guidance on role_slug, replacement-on-change behavior, and singular vs list resources.

Test plan

• Frontmatter/MDX renders correctly in docs preview
• Links and anchors (#managing-app-entitlement-and-connector-ownership) resolve correctly

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
conductorone	🟢 Ready	View Preview	Sep 21, 2026, 4:26 PM

[mindymo]

One open question from a style/content review pass: the role_slug bullet under "Keep in mind" says it's required on every v2 owner resource and that existing configurations set it to "primary", but then asks the reader to confirm that's the value their tenant expects — the field itself is defined as a plain required string in the provider schema with no enforced default or allowed-values list.

Could you confirm whether "primary" is the only supported value, or whether it can legitimately vary by tenant? Right now the doc pushes that uncertainty onto the reader.