feat(consult-transfer): consult transfer popover improvements

[bhabalan]

COMPLETES #< CAI-7397 >

This pull request addresses

Enhancements and UI improvements for Consult/Transfer popover behavior.

• Add loader to each tab in Consult/Transfer popover for better feedback.
• Add a reload button to fetch fresh agent or queue data without switching tabs.
• When performing Consult → Merge (Before attending), if the consult isn’t attended, Transfer button should be hidden or disabled. Basically during ringing state, transfer button should  be disabled
• The End Call button should remain enabled when switching from a consult back to the conference call.

VIDCAST: https://app.vidcast.io/share/2d81de62-3406-4a15-8ff0-887b8e7e4183

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

• The testing is done with the amplify link
  Tested the scenarios in the UI

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
  • Cursor
• 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-570.d1b38q61t1z947.amplifyapp.com

[akulakum]

The End button should remain disabled when performing a switch action during a multi-party conference involving the agent flow, to match the behavior in Agent Desktop.

Steps to Reproduce:

1. Customer, Agent1, and Agent2 are in a conference call.
2. During the conference, Agent1 initiates a consult call to Agent3.
3. Agent3 accepts the consult call, and the call moves to the consulting state.
4. While in this consulting state, if Agent1 performs a switch action, the End button becomes enabled in the CC widgets.
5. However, according to Agent Desktop behavior, the End button should remain disabled during this state.

Expected Behavior:
The End button should be disabled when Agent1 performs a switch action during consult within a multi-party conference, consistent with Agent Desktop.

[akulakum]

The End button should remain enabled when performing a switch action during a 3-party conference involving the entry-point dial number (EP_DN) flow, to match the behavior in Agent Desktop.

Steps to Reproduce:

1. Customer and Agent1 are in a normal call.
2. During the call, Agent1 initiates a consult call to Agent3 (who has EP_DN support enabled) via the Entrypoint tab.
3. Agent3 accepts the consult call, and the call transitions to the consulting state.
4. While in this consulting state, if Agent1 performs a switch action, the End button becomes disabled in the CC widgets.
5. However, according to Agent Desktop behavior, the End button should remain enabled during this scenario.

Expected Behavior:
The End button should remain enabled when Agent1 performs a switch action during consult within a 3-party conference that uses the EP_DN flow, consistent with Agent Desktop.

[akulakum]

Please test the End button behavior across Agent, Queue, External Dial Number, and Entry Point Dial Number flows for consult, three-party, and multi-party conference scenarios.