[Customer Portal][BE]Update case creation and project responses with parentCase and chat support

[cloby99]

• Purpose
  This PR enhances case creation and related response payloads to support parent-child case relationships and chat references.

• Changes
  Updated CaseCreatePayload to accept parentCaseId and chatId fields
  Added related parentCase and chat fields to the case record
  Updated callRequestCreatePayload response
  Updated project response payload structure

Summary by CodeRabbit

Release Notes

• New Features
  • Cases can now reference parent cases and related chats for better case organization and tracking.
  • Project responses now include detailed account information.
  • Call request reason field is now optional.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

The pull request updates entity types and mappings to support case relationships and optional call request reasons. Changes include replacing ProjectResponse's Subscription field with an account record, adding parentCase and chat references to Case types, making CallRequestCreatePayload's reason optional, and updating corresponding mappings.

Changes

Cohort / File(s)	Summary
Entity Type Definitions apps/customer-portal/backend/modules/entity/types.bal	Removes Subscription type entirely; replaces ProjectResponse's Subscription field with optional account record containing id, name, activationDate, deactivationDate, region, etc. Adds optional parentCaseId and chatId to CaseCreatePayload, optional parentCase and chat to Case and CaseResponse, and makes CallRequestCreatePayload's reason field optional (string?).
Type Definitions apps/customer-portal/backend/modules/types/types.bal	Adds two optional reference fields to Case record: parentCase and chat (both ReferenceItem?) for linking to related cases and chats.
Case Mapping Logic apps/customer-portal/backend/utils.bal	Updates searchCases function to map new parentCase and chat fields from case records, each mapped to objects containing id and label properties when present.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Possibly related PRs

• [Customer Portal] Refactor Responses and Record Names #83: Refactors ProjectResponse and Subscription types, directly overlapping with the Subscription removal and account field addition in this PR.
• [Customer Portal][BE] Enhance /projects/{id}/stats/cases endpoint to include additional metrics and cases trend #182: Modifies searchCases mapping logic in utils.bal and updates Case-related type definitions, covering the same code paths affected here.
• [Customer Portal][BE] Update response types, add deployment create endpoint, and refactor filter logic #162: Updates CaseCreatePayload and Case type definitions, particularly relevant to the parentCaseId and parentCase field additions.

Suggested labels

Type/Improvement, App/Customer Portal, Area/Backend

Suggested reviewers

• shayanmalinda
• sacheeramesh

Poem

🐰 Cases now can hold their kin,
With parent links and chats within,
Subscriptions fade, accounts remain—
Relations bloom through diff's domain! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and lacks required template sections (Purpose with issue links, Goals, Approach, User stories, Release note, Documentation, Training, Certification, Marketing, Automation tests, Security checks, Samples, Related PRs, Migrations, Test environment, Learning). Only minimal change details are provided.	Expand the description to include all required template sections: add issue links in Purpose, detailed Goals and Approach, affected User stories, Release note, Documentation impact, and other required sections (or mark as N/A with explanation where not applicable).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly reflects the main changes: updating case creation payloads and project responses to support parentCase and chat references, which aligns with the changeset modifications across multiple files.
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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Rashmika998]

LGTM