Inaccurate Order Handling and Status Updates

Nobody has claimed this yet.

Describe the bug
The Enatega Multivendor Rider App currently exhibits significant issues with order handling and status updates, leading to inaccuracies and potential customer dissatisfaction. When a restaurant accepts an order from the customer app and initiates preparation, riders are notified. However, riders have the capability to assign themselves orders that are still in the preparation stage and mark them as delivered prematurely. This results in discrepancies between the actual status of orders and the information presented to both the restaurant and the customer. Additionally, when riders mark orders as delivered prematurely, the restaurant app considers the order as delivered and registers the payment, even though the order has not been received by the restaurant.

To Reproduce

Restaurant accepts an order from the customer app and starts preparing the order.
Rider receives a notification for the order while it is still in the preparation stage.
Rider assigns themselves the order, even though it is still being prepared.
Rider marks the order as delivered without actually picking it up or completing the delivery.
The restaurant app registers the order as delivered and shows the payment as received, even though the order hasn't been handed over to the rider.
Expected behavior

Riders should only be able to assign themselves orders once they are ready for pickup from the restaurant.
Orders should only be marked as delivered by riders after they have physically received the order from the restaurant and completed the delivery to the customer.
The restaurant app should only consider an order as delivered and register payment after the rider has confirmed delivery, ensuring accurate tracking of order status and payment reconciliation
Screenshots

shah.mp4
**Smartphone **

Device: IOS & Android

Start by tracing order status handling across the rider, restaurant, and customer apps, focusing on assignment, pickup, delivery, and payment transitions described in the reproduction steps. Confirm that assignment is blocked before pickup and that delivery and payment are recorded only after the required handoffs and completed delivery; no files or tests are named in the issue.

Written by the indexing model from the issue text.