Refactor Fertiscan Pydantic Models

## Description
The current Fertiscan Pydantic models need to be better aligned with our database schema. There is also a naming conflict between the `Inspection` Pydantic model, which is designed as an overarching object containing other models, and the `Inspection` database table, which primarily contains references (IDs) to other tables. Additionally, the `Inspection` model is missing few attributes like `PictureSet` and `Sample`.

## Tasks
- Review and update all Fertiscan Pydantic models to ensure they closely mirror their corresponding database tables, including adding an `id` field where necessary.
- Create a new Pydantic model for the `Inspection` database table that accurately represents its structure.
- Rename the existing `Inspection` model to avoid conflict with the `Inspection` database table.
- Revise the `Inspection` model to include the missing attributes such as `PictureSet` and `Sample`.
- Create the `PictureSet` and `Sample` models, along with any other models needed for existing database tables.
- Update the `build_inspection_import` and `build_inspection_export` functions to reflect the changes in the `Inspection` model and other related models.
- Update all references in the codebase to use the newly named and updated models.
- Ensure all models are correctly linked and reflect the changes made.
- Write tests to confirm that the new and updated models and functions work correctly.
- Ensure all tests pass after making these changes.