Clarify cloud vs VuMark database tests with split classes

[adamtheturtle]

Summary

Split TestAddDatabase into TestAddCloudDatabase and TestAddVuMarkDatabase, and TestDeleteDatabase into TestDeleteCloudDatabase and TestDeleteVuMarkDatabase. Updated docstrings and method names to explicitly reference "cloud database" or "VuMark database" for clarity and better test organization.

Changes

• Separated database type tests into dedicated classes for cloud and VuMark databases
• Updated class docstrings to specify database type
• Updated method docstrings to mention "cloud database" or "VuMark database"
• Renamed test_delete_database to test_delete_cloud_database in the cloud database class
• Simplified method names in VuMark-specific class by removing redundant "vumark" prefix (class name provides context)

---

Note

Low Risk
Test-only refactor that primarily renames/reorganizes classes and docstrings without changing production logic.

Overview
Refactors the Flask usage tests to separate cloud vs VuMark database coverage by splitting the old add/delete database test classes into TestAddCloudDatabase/TestAddVuMarkDatabase and TestDeleteCloudDatabase/TestDeleteVuMarkDatabase.

Updates test/docstring wording and a cloud delete test name (test_delete_cloud_database) to explicitly reference the database type, and relocates the “create cloud database with no details” test into the cloud-specific class.

^{Written by Cursor Bugbot for commit 1894163. This will update automatically on new commits. Configure here.}