Consolidate duplicate API endpoints - API v1 vs non-API routes

The app has significant endpoint duplication between API v1 (used by Behat tests) and non-API routes (used by frontend). This creates maintenance burden and potential inconsistencies. And actually we're testing in Behat endpoints that not used by FE. 😕 Here some examples:

• Table Creation

  • API v1 (behat tests): POST /api/1/tables → Api1Controller::createTable()
  • Non-API (frontend): POST /table → TableController::create()
  • API v2 (OCS): POST /api/2/tables → ApiTablesController::create()

• View Creation

  • API v1 (behat tests): POST /api/1/tables/{tableId}/views → Api1Controller::createView()
  • Non-API (frontend): POST /view → ViewController::create()

• Row Creation in Table

  • API v1 (behat tests): POST /api/1/tables/{tableId}/rows → Api1Controller::createRowInTable()
  • API v2 (OCS): POST /api/2/tables/{nodeId}/rows → RowOCSController::createRow()

And much more... Would be nice to move to V2 everywhere to get rid of the duplication. Related to #713

Start by comparing the endpoint implementations in lib/Controller/Api1Controller.php, TableController.php, ViewController.php, ApiTablesController.php, and RowOCSController.php, along with the Behat tests and frontend callers. Map which API v1 and non-API routes are still used, then determine the migration scope for API v2. Done means the active consumers use the consolidated endpoints, redundant routes and tests are addressed, and behavior remains consistent.