Feature Request: Support for $web container and Static Website hosting emulation

### Summary
Is there any plan to support the `$web` container and static website hosting feature in Azurite, consistent with Azure Blob Storage?

### Motivation & Use Case
In Azure Blob Storage, enabling static website hosting allows serving static content (HTML, CSS, JS, images) directly from a special container named `$web`, supporting features like default index document (`index.html`) and error document paths (`404.html`).

Currently, when developing and testing applications locally with Azurite:
1. Emulating the `$web` container and static website hosting behavior is not fully supported out-of-the-box compared to the real Azure environment.
2. Local integration testing and development workflows for SPAs or static assets deployed to Azure Blob Storage require workarounds or connecting to a live Azure Storage account.

### Proposed Feature / Solution
- Allow the creation, management, and API access of the special `$web` container in Azurite Blob service.
- (Ideal) Support static website endpoint emulation to serve index and error documents locally over HTTP.

### Additional Context
Having `$web` container support would greatly improve local development fidelity and CI/CD automated testing for frontend/serverless architectures targeting Azure Storage.

The issue identifies the Azurite Blob service, the special `$web` container, and static website hosting, but names no files or tests. Start by locating existing Blob service container handling and the relevant HTTP endpoint entry points, then compare them with Azure Blob Storage behavior. Done means `$web` can be managed and accessed locally, with static website behavior defined and covered by tests.

Written by the indexing model from the issue text.