fix(cc-components): show dialed number instead of entrypoint for outdial calls

[bhabalan]

COMPLETES

https://jira-eng-sjc12.cisco.com/jira/browse/CAI-7359

This pull request addresses

When making an outdial call via dialpad, the IncomingTask, TaskList, and active task (CallControlCAD) were displaying the entrypoint/ANI number instead of the actual dialed destination number. This affected all three task display areas and occurred on every outdial call.

by making the following changes

• incoming-task.utils.tsx: Check interaction.outboundType to detect outdial calls and use dn (dialed number) from callAssociatedDetails instead of ani (entrypoint) for the task title
• task-list.utils.ts: Same fix applied for the task list item title display
• call-control-cad.tsx: For outdial calls, swap ani and dn so the dialed number appears as the primary customer identifier and the entrypoint number appears as the secondary phone number

Change Type

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tooling change
• Internal code refactor

The following scenarios were tested

• Unit tests — all 632 cc-components tests passing
• Verified outdial detection logic via interaction.outboundType field
• Inbound calls continue to show ani as expected (no regression)

The GAI Coding Policy And Copyright Annotation Best Practices

• GAI was not used (or, no additional notation is required)
• Code was generated entirely by GAI
• GAI was used to create a draft that was subsequently customized or modified
• Coder created a draft manually that was non-substantively modified by GAI (e.g., refactoring was performed by GAI on manually written code)
• Tool used for AI assistance (GitHub Copilot / Other - specify)
  • Github Copilot
  • Other - Claude Code
• This PR is related to
  • Feature
  • Defect fix
  • Tech Debt
  • Automation

Checklist before merging

• I have not skipped any automated checks
• All existing and new tests passed
• I have updated the testing document
• I have tested the functionality with amplify link

---

Make sure to have followed the contributing guidelines before submitting.

[aws-amplify-us-east-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-655.d1b38q61t1z947.amplifyapp.com