Issue: [BUG]Noon Connector V2 API Failure - Missing order_category in Authorize flow

### Bug Description

The Noon Connector V2 API is failing in the payment flow with the error “Missing required param: order_category.” This happens because the connector_metadata is not being extracted properly in the V2 confirm-intent flow, which causes the order_category field to be None. 

### Expected Behavior

The Noon Connector V2 API should extract order_category from connector_metadata during the payment flow. When a request with valid connector_metadata is sent, the order_category value should be passed correctly to the connector, and the payment should proceed without errors.

### Actual Behavior

The connector_metadata is not being extracted in the V2 payment flow, causing the `order_category` field to be None. As a result, the API returns the error `Missing required param: order_category`, and the payment flow fails to complete.

### Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'


### Context For The Bug

_No response_

### Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the `x-request-id` response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:
1. Operating System or Linux distribution:
2. Rust version (output of `rustc --version`): ``
3. App version (output of `cargo r --features vergen -- --version`): ``


### Have you spent some time checking if this bug has been raised before?

- [x] I checked and didn't find a similar issue

### Have you read the Contributing Guidelines?

- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

Yes, I am willing to submit a PR!

Resolution: <think>
PR Context:
- Title: fix(payments): add connector metadata parsing and order category to payment router data
- Merged: 2025-10-16T10:25:01Z
- Files changed: 8 files
- Commits: 2 commits

Implementation approach:


## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
The Noon Connector V2 API is failing in the payment flow with the error `Missing required param: order_category.` This happens because the connector_metadata is not being extracted in the V2 confirm-intent flow, which causes the order_category field to be None. The fix involves co
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(payments): add connector metadata parsing and order category to payment router data (#9825)
Files to modify:


**crates/api_models/src/payments.rs**
  Modify existing code

**crates/hyperswitch_domain_models/src/payments.rs**
  Remove:
    - function: pub::get_optional_connector_metadata

**crates/hyperswitch_domain_models/src/payments/payment_intent.rs**
  Modify existing code

**crates/router/src/core/payments/operations/payment_update_intent.rs**
  Modify existing code

**crates/router/src/core/payments/transformers.rs**
  Modify existing code

**crates/router/src/core/utils.rs**
  Modify existing code

**crates/router/src/services/kafka/payment_intent.rs**
  Modify existing code

**crates/router/src/services/kafka/payment_intent_event.rs**
  Modify existing code