CRUD Personas

[rquesada]

Summary

This PR modifies the object Persona and PersonaCreate, changing the fields voiceId to Voice object and faceId to Face object

Changes

• Added Voice schema
• Added Face schema
• Modified Persona
• Modified PersonaCreate

Related Issues

N/A

Type of Change

This change solved the comments posted on the review of the previous PR created by @rquesada [https://github.com//pull/4]

Checklist

• I have read the CONTRIBUTING documentation.
• I have performed a self-review of my own code.
• I have added tests that prove my fix is effective or that my feature works.
• I have updated the documentation (if applicable).

Screenshots (if applicable)

Additional Context

Tested locally using Swagger.
Based on the premise that we are not expecting that faces and voices to be modified frequently, so the approach we considered here was to create an "assets" folder (in the front-end) to store the images, videos and audios. Then it was only going to be necessary to store the id of voice and face to help us associate the asset with the voice and face.

For example:
Given the object Persona:

      {
        "name": "Mari",
        "description": "Mari A",
        "voiceId": "x4te5a69-40d6-4246-8d53-f4c777be8080",
        "faceId": "7ffe5a69-40d6-4246-8d54-f4c777be6989",
        "id": "91a7542f-da52-46ab-85b9-08f871722e93"
      }

The frontend will be able to load the files:
:/assests/audio/x4te5a69-40d6-4246-8d53-f4c777be8080.mp3
:/assests/face/7ffe5a69-40d6-4246-8d54-f4c777be6989.jpg
:/assests/video/7ffe5a69-40d6-4246-8d54-f4c777be6989.mp4

[samj]

You've got a merge done through the GitHub UI/API (e4b4044) and it looks like you've replaced OpenAI's openapi.yaml with ours.

[rquesada]

A new PR was created to fix the comments @samj