ENGG-5057 Fix ts errors in HTTPRequestTabs

Walkthrough

This PR removes the HttpRequestTabs component and its exported types from app/src/features/apiClient/screens/apiClient/components/views/components/request/components/RequestTabs/, and deletes the associated SCSS file for the request tabs. Separately, it modifies a different HttpRequestTabs implementation at app/src/features/apiClient/screens/apiClient/components/views/http/components/HttpRequestTabs/ by adding a getContentTypeWithAlert callback, Sentry captureException usage, defensive defaults for body, and adjusted hook dependencies. A minor null-safety change was also made in HttpClientView to use optional chaining when reading response time.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

• Mixed changes: full-file/component deletion + targeted runtime-safety edits in a separate component.
• Areas needing attention:
  • Confirm no remaining references/imports to the deleted RequestTabs or its enum/props.
  • Verify Sentry captureException usage and that getContentTypeWithAlert dependency coverage is correct.
  • Ensure body defaulting and optional chaining do not alter intended behavior in edge cases.

Possibly related PRs

• [AI-11] Feat: AI tests generation support in API Client #3919 — edits to RequestTabs and ScriptEditor integration that overlap with the removed RequestTabs component.
• [ENGG-4727] fix: green dot tab indicator for param and body tabs #3757 — changes within the HttpRequestTabs implementation that overlap with the modified file in this PR.
• [ENGG-5051] fix: ts errors in HttpClientView #3995 — introduces null-safety and prop-type adjustments in HttpRequestTabs, related to the runtime-safety changes here.

Suggested reviewers

• RuntimeTerror10
• rohanmathur91
• TejaChitturi

Pre-merge checks and finishing touches

Learnt from: CR
Repo: requestly/requestly PR: 0
File: .cursorrules:0-0
Timestamp: 2025-11-25T09:03:46.345Z
Learning: Follow existing code style and patterns in the Requestly project

Learnt from: mustafa-sayyed
Repo: requestly/requestly PR: 3723
File: app/src/features/apiClient/screens/apiClient/components/views/http/components/HttpRequestTabs/HttpRequestTabs.tsx:146-151
Timestamp: 2025-10-22T22:57:45.959Z
Learning: In the API Client Scripts tab (app/src/features/apiClient/screens/apiClient/components/views/http/components/HttpRequestTabs/HttpRequestTabs.tsx), the dot indicator should only appear when scripts are present (count > 0). When no scripts exist, the dot should not be rendered. This is the intended behavior per issue #3731.

Learnt from: nafees87n
Repo: requestly/requestly PR: 3655
File: app/src/features/apiClient/screens/apiClient/components/views/components/Collection/components/CollectionRunnerView/components/RunResultView/RunResultContainer/RunResultContainer.tsx:426-426
Timestamp: 2025-10-10T11:08:23.369Z
Learning: In the file `app/src/features/apiClient/screens/apiClient/components/views/components/Collection/components/CollectionRunnerView/components/RunResultView/RunResultContainer/RunResultContainer.tsx`, the `destroyInactiveTabPane={true}` setting is intentional. The loss of state (expandedKeys, scroll position) when switching tabs is acceptable for now and will be addressed in future work.

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.

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

@coderabbitai review