Domain: model Blob Container and Blob Item

Goal

Model the two other core concepts users work with: blob containers and the blobs inside them.

Why

Everything in the app's core workflow (browsing, uploading, downloading) revolves around containers and blobs; we need a stable, SDK-agnostic representation before wiring up any Azure SDK calls.

Tasks

• Add a BlobContainerInfo entity (name, last modified, public access level, metadata).
• Add a BlobItem entity/value object (name/path, size, content type, last modified, ETag, access tier, metadata).
• Model blob "virtual folders" (blobs are stored flat but commonly browsed as folders via / delimiters) so the future UI can render a folder tree.
• Add unit tests for folder-path parsing (e.g. folder/sub/file.txt → folder segments + leaf name).

Acceptance Criteria

• BlobItem/BlobContainerInfo carry enough data to render a Storage-Explorer-like listing.
• Folder-path parsing is covered by unit tests including edge cases (root-level blobs, trailing slash, nested folders).

Start by locating the project’s model structure and the planned BlobContainerInfo and BlobItem entities. Define the container and blob data needed for a Storage-Explorer-like listing, model virtual folder segments, and add unit tests for root-level, trailing-slash, and nested paths; done means the acceptance criteria and all parsing edge cases pass.