Corrected "submitted_at" description on order schemas

Broker API

The submitted_at description on the Order and OrderLeg schemas previously stated that the value may be before created_at. Because orders are submitted for execution asynchronously to database updates, submitted_at may in fact be after created_at. The documentation now reflects the actual behavior; the response shape is unchanged.

Affected Endpoints

• POST /v1/trading/accounts/{account_id}/orders
• GET /v1/trading/accounts/{account_id}/orders
• GET /v1/trading/accounts/{account_id}/orders/{order_id}
• GET /v1/trading/accounts/{account_id}/orders:by_client_order_id
• PATCH /v1/trading/accounts/{account_id}/orders/{order_id}
• DELETE /v1/trading/accounts/{account_id}/orders
• POST /v1/trading/accounts/{account_id}/orders/estimation
• DELETE /v1/trading/accounts/{account_id}/positions
• DELETE /v1/trading/accounts/{account_id}/positions/{symbol_or_asset_id}
• GET /v1/rebalancing/runs
• GET /v1/rebalancing/runs/{run_id}
• GET /v2/events/trades