feat: add sampleName field to Sample schema

[Junjiequan]

Description

This PR adds sampleName field to the Sample schema. Since existing samples were created without this field, a migration has been added to backfill sampleName with the existing sampleId value.

Motivation

Fixes

• Bug fixed (#X)

Changes:

• changes made

Tests included

• Included for each change/fix?
• Passing?

Documentation

• swagger documentation updated (required for API changes)
• official documentation updated

official documentation info

Summary by Sourcery

Add a required sampleName field to the Sample model and backfill existing records from sampleId.

New Features:

• Introduce sampleName as a required field on the Sample schema and update DTOs to accept it.

Enhancements:

• Add a one-way migration to populate sampleName for existing Sample documents using their sampleId values.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• In UpdateSampleDto, sampleName is marked as required, which may break existing partial update flows; consider making it optional or aligning its validation with how PATCH/partial updates are intended to work for this resource.
• The migration down method is currently a no-op; if rollback is expected in your migration flow, consider unsetting sampleName on documents where it was backfilled to avoid leaving irreversible data shape changes.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `UpdateSampleDto`, `sampleName` is marked as required, which may break existing partial update flows; consider making it optional or aligning its validation with how PATCH/partial updates are intended to work for this resource.
- The migration `down` method is currently a no-op; if rollback is expected in your migration flow, consider unsetting `sampleName` on documents where it was backfilled to avoid leaving irreversible data shape changes.

## Individual Comments

### Comment 1
<location path="src/samples/dto/update-sample.dto.ts" line_range="26" />
<code_context>
+   */
+  @IsString()
+  @IsNotEmpty()
+  readonly sampleName: string;
+
   /**
</code_context>
<issue_to_address>
**question:** Consider whether `sampleName` should be optional in an update DTO

For an update DTO, requiring `sampleName` means every update must supply it, even when modifying other fields only. If this endpoint is intended for partial updates, consider marking `sampleName` as `@IsOptional()` and `readonly sampleName?: string`, and keep it required only in the create DTO. If updates are meant to be full replacements, this is fine—just confirm it aligns with the API contract.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}