[Bug] 100MB database quota not enforced

[GGWPVV]

Discription

• Database size limit of 100MB per user is not enforced, allowing users to exceed the quota and causing financial losses to the provider

Preconditions:

• User has an active account in Oblache system
• User has access to database creation and data insertion capabilities

Reproduction steps:

1. Create a database
2. Connect to the database using provided credentials
3. Insert large amounts of data (e.g., using bulk insert scripts)
4. Continue inserting data beyond the 100MB limit

Expected Result:

1. System should block database writes when approaching 100MB limit
2. Database should transition to read_only_threshold status according to design_doc.md(№5)
3. User should receive error messages when attempting to insert more data
4. No data insertion should be possible beyond 100MB quota

Actual result:

1. System allows unlimited data insertion beyond 100MB quota
2. Database remains in normal operational state
3. No quota enforcement mechanisms are triggered
4. User can insert 1.4GB+ of data without any restrictions

What we see after we reproduced the bug

Environment:

• OS: Windows 11 Home 64-bit (10.0, Build 26100)
• Browser: Chrome/140.0.0.0
• URL: https://oblache.areso.pro/profile.html

Priority(High, Medium, Low)

• High

Severity(Blocker, Critical, Major, Minor, Trivial)

• Critical

Application:
-Oblache Database-as-a-Service platform

Link to Allure report:
https://areso.github.io/Oblache/

Additional context