feat: add lifecycle hooks to page objects (_before, _after, _afterSuite) (#5512)

Page objects now support lifecycle hooks that mirror the helper hook system.
_before() runs lazily on first method call per test, _after() runs after
each test for used page objects, and _beforeSuite()/_afterSuite() run for
all page objects that define them. Also documents Data Objects pattern for
REST-based test data management with automatic cleanup.

Co-authored-by: DavertMik <davert@testomat.io>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: 3 people

docs/data.md

@@ -18,7 +18,11 @@ The most efficient way would be to allow test to control its data, i.e. the 3rd
 However, accessing database directly is not a good idea as database vendor, schema and data are used by application internally and are out of scope of acceptance test.
 
 Today all modern web applications have REST or GraphQL API . So it is a good idea to use it to create data for a test and delete it after.
-API is supposed to be a stable interface and it can be used by acceptance tests. CodeceptJS provides 4 helpers for Data Management via REST and GraphQL API.
+API is supposed to be a stable interface and it can be used by acceptance tests. CodeceptJS provides helpers for Data Management via REST and GraphQL API, as well as **[Data Objects](/pageobjects#data-objects)** — class-based page objects with automatic cleanup via lifecycle hooks.
+
+## Data Objects
+
+For a lightweight, class-based approach to managing test data, see **[Data Objects](/pageobjects#data-objects)** in the Page Objects documentation. Data Objects let you create page object classes that manage API data with automatic cleanup via the `_after()` hook — no factory configuration needed.
 
 ## REST