Added delete_namespace docs

[ilongin]

Added docs for delete_namespace and fix current docs formatting.

Summary by Sourcery

Add documentation for the delete_namespace function in the namespaces guide, including its signature, behavior, and usage examples, and correct existing formatting issues.

Enhancements:

• Fix formatting inconsistencies in the namespaces guide

Documentation:

• Document the delete_namespace function with details on removing empty namespaces or projects
• Include the function signature, parameter descriptions, and behavior constraints
• Add usage examples demonstrating namespace and project deletion

[sourcery-ai]

Reviewer's Guide

This PR updates the namespaces guide by closing an unclosed code block and appending comprehensive documentation for the delete_namespace function, including its signature, usage rules, and examples.

File-Level Changes

Change	Details	Files
Corrected documentation code block formatting	Closed the existing code snippet with ``` Inserted a blank line before the new section	docs/guide/namespaces.md
Added documentation for delete_namespace	Introduced “Removing Namespaces and Projects” section Defined the delete_namespace signature and behavior Outlined deletion rules for namespaces and projects Provided usage examples	docs/guide/namespaces.md

Possibly linked issues

• remove docstring from DataModel.__pydantic__init_subclass__ #123: The PR adds delete_namespace documentation and corrects the formatting of existing documentation as described in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

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.}

[cloudflare-workers-and-pages]

Deploying datachain-documentation with    Cloudflare Pages

Latest commit:	0faaf95
Status:	✅  Deploy successful!
Preview URL:	https://573c9782.datachain-documentation.pages.dev
Branch Preview URL:	https://ilongin-1338-namespaces-docs.datachain-documentation.pages.dev

View logs

[shcheklein]

check the layout (periods), etc

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.57%. Comparing base (21e7e09) to head (0faaf95).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1339   +/-   ##
=======================================
  Coverage   87.57%   87.57%           
=======================================
  Files         156      156           
  Lines       14502    14502           
  Branches     2083     2083           
=======================================
  Hits        12700    12700           
  Misses       1331     1331           
  Partials      471      471           

Flag	Coverage Δ
datachain	87.50% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/datachain/__init__.py	100.00% <100.00%> (ø)
src/datachain/lib/namespaces.py	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

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

[shcheklein]

@ilongin tests fail

[amritghimire]

Also, even though 12 tests failed, I could see squash and merge cc @0x2b3bfa0