refactor: organize types by kind

[lihbr]

Types of changes

• [x] Chore (a non-breaking change which is related to package maintenance)
• [ ] Bug fix (a non-breaking change which fixes an issue)
• [ ] New feature (a non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Refactor the really long type definition files into multiple, smaller ones, for readability.

• Every field type has its own file
  • Rich Text and Title types are kept within the same file
  • Same for all link types
  • Same for Slice Zone types
• File tree is the same between customTypeModelFields and fields (apart from deprecated models)
• CustomTypeModel lives in its own files at root, as it's the analog of PrismicDocument

Any comment/improvement suggestions on this logic? I really think it eases readability and maintainability when split into multiple files like this.

Checklist:

• [ ] My change requires an update to the official documentation.
• [x] All TSDoc comments are up-to-date and new ones have been added where necessary.
• [x] All new and existing tests are passing.

🦎

[codecov-commenter]

Codecov Report

Merging #47 (bc7d242) into master (bb88ccd) will not change coverage. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            master       #47    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files            4         7     +3     
  Lines         1774      1614   -160     
  Branches         7         6     -1     
==========================================
- Hits          1774      1614   -160     

Impacted Files	Coverage Δ
src/fields/embed.ts	100.00% <100.00%> (ø)
src/fields/index.ts	100.00% <100.00%> (ø)
src/fields/link.ts	100.00% <100.00%> (ø)
src/fields/richText.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[lihbr]

Looking good to me, but I'll wait for your green mark :)

[angeloashmore]

Looks great! Merging & deploying.