feat: integrate update_property non implemented functions on main db

[mcllerena]

This PR addresses Issue #179 implementing:

• A property update support for both single-record and bulk workflows.
• Adds update_property() with corresponding additional configuration params.
• Scalability processing through batching and executemany().
• Reusable code across CRUD operations.
• Update documentation for operation examples.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 86.66667% with 22 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.76%. Comparing base (6caf473) to head (73afe89).

Files with missing lines	Patch %	Lines
src/plexosdb/db.py	86.92%	20 Missing ⚠️
src/plexosdb/utils.py	81.81%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #170      +/-   ##
==========================================
- Coverage   96.15%   95.76%   -0.40%     
==========================================
  Files          20       20              
  Lines        3097     3235     +138     
==========================================
+ Hits         2978     3098     +120     
- Misses        119      137      +18     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pesap]

Please address the inline findings before merging. The update implementation should reuse the existing property validation and membership-resolution paths, and follow the established bulk insertion pattern for batch execution. Keep update_property() as a thin public wrapper; removing the shared helper is not required if it cleanly centralizes the selector logic. Please also add coverage for rollback after domain-validation failures, scenario-scoped updates, explicit parent membership selection, and reusing the connection after a failed batch.

[mcllerena]

@pesap you can check it out again.