Developer Plan Updates Technical Investigation

[katia-sentry]

Details about this task in the parent issue: #2778

• This is V1: Replace free plan with team plan.
• existing plans are grandfathered in, meaning the former free plans experience stay as-is

Tasks:

• Collaborate with Product and Design to ensure technical feasibility and align with user experience goals.
• Documentation and Task Breakdown:
  • Document project initiatives and plans in Notion,
  • Create actionable GitHub issues in Update UIs for the New Developer Plan #2778
  • Organize tasks, categorizing by UI and API components.
• List and include all project team members in relevant discussions and updates.
• Define clear deadlines and milestones for the project and communicate progress.

Outcomes:
Develop a clear implementation plan for this feature, with technical and design considerations, broken down into actionable development tickets.

Reference:
Guide for leading a project: https://www.notion.so/sentry/Project-Guideline-for-Engineers-37b967598a834e9ebc5bde2608d9c2f7

[ajay-sentry]

@katia-sentry After talking with @RulaKhaled, we're going to split the investigation into two separate workstreams:

1. Investigate what a "Plan Configuration" Model can look like and the respective GQL Api to follow
2. Investigate how long it would take (and if its possible) to consolidate all the Backend Plan types/interfaces into a unified interface in Shared

Depending on bandwidth required for #1 we think this would be a reasonable route to take this quarter to expedite any plan configuration updates, modifications, deprecations, etc. for the foreseeable future.

CC: @aj-codecov