Update Price

>Update product price in prices table in Database

#### Pre-requisites:
- [ ] complete price module
- [ ] complete products module.
- [ ] price model
- [ ] price service (update End_date )
- [ ] price DAO(update End_date )
- [ ] price service (create price)
- [ ] price DAO(create price)

#### Validations:

- [ ] Form validation
- Product price input validation(product_id,price)
- price (empty)
- price > 0 && price < 5000
- [ ] business validation
- Product already exist (if product id )
- Product price already exist (if the end date exists)

#### Messages:
* Product id should be above 0
* Product name cannot be null or empty
* Product description cannot be null or empty
* Product_id does not exists
* Product price already exists

#### Flow:
```mermaid
graph TD;
A[price Service: Update product price] --> B[Form Validation]
B -- yes --> C("business validaton( Product_id already Exist)")
C --- Yes --> F(Business validation : price id exist)
F---yes --> Z["Price Service: Update end price"]
Z --> G["Price Service: create price"]
G--> H["Price DAO: create price"]
H--> I["Price Service: Product Price Created"]
F---No--> J["Price Service: price id not exist"]
C -- No --> K["Price Service : Product does not exist"]
B -- No --> L["Price Service : Invalid input"]

Start by locating the price model, price service, price DAO, and products module referenced in the issue; no file paths or tests are provided. Trace the update-end-date and create-price flow, then verify the listed form, business validations, and messages. Done means the price update flow handles the specified validations and creates the new price record.

Written by the indexing model from the issue text.