CR: "Decision Suite" should be the same in Registrations and APplications in the examiner dashboard

Current view of an application decision UX;

Current view of registration UX:

Please back-port the "Decision Component" from the Registration Detail page into the Application Detail page.

This is only needed for new applications because once an application becomes a registration, the application is no longer useful.

For the decision suite on an application:

make it behave the exact same way as the decision suite on the registration with the following exceptions:

1. The Cancel button label will be refuse instead of cancel
2. under More actions, replace the Suspend Registration with a 'Withdraw Application' action:

The refuse button works the same as refuse currently does on the application decision (makes the status declined).
The Withdraw application decision behaves the same way the cancel/refuse button does.

## Acceptance Criteria
> Generated by [Zenhub AI](https://www.zenhub.com/ai)

### Acceptance Criteria

- [ ] **Scenario: Decision Component UI Consistency**
- Given I am an examiner viewing an Application Detail page
- When I view the decision suite section
- Then it should be visually and structurally identical to the Decision Component found on the Registration Detail page

- [ ] **Scenario: Refuse button labeling and functionality**
- Given I am viewing the Decision Component on an Application Detail page
- Then the action button that is labeled "Cancel" on the Registration page must be labeled "Refuse"
- When I click the "Refuse" button and confirm the action
- Then the application status should be updated to "declined"

- [ ] **Scenario: More Actions menu customization**
- Given I am viewing the "More actions" dropdown within the Decision Component on an Application Detail page
- Then I should see an option for "Withdraw Application"
- And I should not see an option for "Suspend Registration"

- [ ] **Scenario: Withdraw Application functionality**
- Given I am viewing the "More actions" dropdown on an Application Detail page
- When I select the "Withdraw Application" action
- Then the application should be processed using the same logic as the "Refuse" action (e.g., status update and confirmation flow)

- [ ] **Scenario: Component Scope**
- Given an application has not yet been converted into a registration
- Then the updated Decision Component should be visible on the Application Detail page
- Given an application has already become a registration
- Then the standard Registration Detail page view should persist (no changes to existing registration logic)

Start at the Application Detail and Registration Detail pages, comparing their existing decision suites and the current application decision behavior. Implement the application-specific Refuse and Withdraw Application actions without changing registration behavior, then verify the UI, confirmation flow, and declined status against every acceptance criterion.

Written by the indexing model from the issue text.