feat: Extract and log blob metadata (size, last-modified) in MyFirstBlobFunction

[the-damian]

Blob uploads are our data trigger, but we're only logging the path—add file size and last-modified time for audit trails! Use myblob.length and myblob.last_modified to log extras (e.g., "Blob: People.csv, Size: 1024 bytes, Modified: 2025-10-01"). Optional: Append to a new blob (newcontainer/metadata.log) for persistence. This turns basic watching into traceable storage workflows, essential for our serverless dashboard dreams.

[hey-farhan]

Blob uploads are our data trigger, but we're only logging the path—add file size and last-modified time for audit trails! Use myblob.length and myblob.last_modified to log extras (e.g., "Blob: People.csv, Size: 1024 bytes, Modified: 2025-10-01"). Optional: Append to a new blob (newcontainer/metadata.log) for persistence. This turns basic watching into traceable storage workflows, essential for our serverless dashboard dreams.

Implemented blob metadata logging as requested! The solution:

✅ Added logging for blob size and last-modified timestamp using native properties
✅ Implemented the optional persistent storage feature (metadata.log)
✅ Added proper error handling around the storage operations
✅ Updated README to document the new functionality

This feature enhances our audit capabilities by providing visibility into the file characteristics that trigger our serverless functions. The

implementation is lightweight yet robust, with graceful error handling for production reliability. The persistent log option provides a historical record that survives beyond function execution context.

i will be raising PR for a separate branch , please review it and merge if you approve of my solution .

[the-damian]

Ok , Go ahead.