Feat/looking for field-21- Implement the “Looking for” list in ProjectDetail page.

[leonardohervert]

What does this PR do?

Implement the "Looking for" field, to add the required or necessary disciplines in the project, this PR adds the schema, seeds.

Where should the reviewer start?

app/pages/projects/[projectId]/index.tsx app/disciplines/queries/getDisciplines.ts app/projects/components/ProjectForm.tsx app/projects/mutations/updateProject.ts app/projects/mutations/createProject.ts app/projects/mutations/deleteProject.ts

How should this be manually tested?

1. In the home page create a new Proposal
2. Fill the default fields and add more details
3. Fill the new field of "Looking For" to add the disciplines that the project need
4. Create the project, and you could see the disciplines under the skills area.

Screenshots

Checklist

• [x] I added the disciplines schema.
• [x] I added some discipline seeds.
• [x] I create the component to add, edit or delete disciplines in a project.
• [x] I update the mutations for create, update, delete a project.

Issue #21

[jackbravo]

And I would say we can just separate the seed, and make sure we are importing it on the main seed. But I would leave modifying the CI for a separate PR or task, since for now we will be able to run it manually on prod only once.

[leonardohervert]

I already create both files, please check if I am right

[LuisTejedaS]

@jackbravo @leonardohervert let's keep in mind that we should be aware of modifying CI/CD before the next prod release or not forget to seed manually once deployed. Otherwise, users may feel that the feature is either incomplete or buggy.