upload new track

user Story

user will successfully upload track

### Pre-requisites:-

- [ ] Completed feature 1 - create user
- [ ] track table
- [ ] track model
- [ ] track dao (create)
- [ ] track service(create)
- [ ] track price table
- [ ] track price model
- [ ] track price dao(create)
- [ ] track price service(create)
- [ ] asset table
- [ ] asset model
- [ ] asset dao(create)
- [ ] asset service (create)

#### Validations:

- [ ] Form validator
* track object (null)
* track name (null, empty,pattern)
* track price(null,empty,0)
* asset audio(ext,url)
* asset image(ext,url)
#### Messages :
* audio/image invalid format type
* price must be not 0 or not null
* track name is empty or null

#### Flow:

> Invalid When a track details or image / audio format and name is null or when the input provided does not meet the criteria, users arise.
​
```mermaid

graph TD;

A(track service argument track object)-->B(Form Valiation)--valid-->C(Business Validation)
B--Invalid-->D(Validation Exception)
C--valid-->E(Track dao)
C--Invalid-->F(validation Exception)
E-->I(result)-->asset_service-->G(Form validation)
G--valid-->H(asset Dao)
G--Invalid-->J(validation Exception)
H-->O(result)
O-->Q(track price service)
Q-->P(Form validation)
P--valid-->S(track price dao)
P--Invalid-->T(validation exception)
S-->V(Stored in database)
```

Inizia individuando i modelli, i DAO e i servizi relativi a track, prezzo del track e asset, quindi esamina la funzionalità create-user completata per verificare le convenzioni del progetto. Implementa il flusso di upload e le validazioni del modulo e di business elencate, inclusi i formati audio/immagine, il nome e il prezzo, e verifica che i dati validi vengano memorizzati nel database.

Scritto dal modello di indicizzazione a partire dal testo della issue.