refactor: move Record and Response schemas to his own file and unify canonical schemas for them

[jfcalvo]

Description

This is the first of a collection of PRs that will include changes to our Pydantic schemas used by our API v1 endpoints.

The changes included in this PR are the following:

• Now we have only one Record canonical schema used by all API v1 endpoints.
  • The schemas related with records has been moved to schemas/v1/records.py module.
  • The canonical Record schema is now including dataset_id as attribute in all cases.
• Now we have only one Response canonical schema used by all API v1 endpoints.
  • The schemas related with responses has been moved to schemas/v1/responses.py module.
  • The canonical Response schema is now including record_id as attribute in all cases.

Refs #4407

Type of change

(Please delete options that are not relevant. Remember to title the PR according to the type of change)

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (change restructuring the codebase without changing functionality)
• Improvement (change adding some improvement to an existing functionality)
• Documentation update

How Has This Been Tested

• Running and modifying unit tests.

Checklist

• I added relevant documentation
• follows the style guidelines of this project
• I did a self-review of my code
• I made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I filled out the contributor form (see text above)
• I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)