improvement: Retail example JSONs

[rajaneeshk90]

Description

This PR updates the retail example JSON payloads to improve consistency across request and response samples.

The changes are limited to example files under examples/ and focus on aligning pricing, commitment references, and a few response payload details.

Changes Made

• Added price objects in example payloads where applicable
• Added offerId in RetailCommitment examples
• Updated line-item price values to reflect quantity-based totals
• Added serviceability details in selected response examples
• Removed paymentMethods from certain status response examples
• Fixed a duplicated breakup entry in examples/select/on_select-response.json

Files Updated

• examples/cancel/cancel-request.json
• examples/cancel/on_cancel-response.json
• examples/confirm/confirm-request.json
• examples/confirm/on_confirm-response.json
• examples/init/init-request.json
• examples/init/on_init-response.json
• examples/select/on_select-response.json
• examples/select/select-request.json
• examples/status/on_status-response-1.json
• examples/status/on_status-response-2.json
• examples/status/on_status-response-3.json
• examples/status/status-request.json
• examples/update/on_update-response.json

Why

These updates make the sample retail flows more internally consistent and more representative of actual pricing and fulfillment-related data.

Expected Outcome

• Example payloads better reflect item pricing and total line values
• Commitments consistently reference the associated offer
• Response examples are clearer for implementers using these sample files

Testing

• Verified JSON example updates in the modified sample files
• No code or schema changes included in this PR

Notes

This PR is limited to sample/example payload improvements only.