docs(config): Updated configuration documentation and feature flag comments

- Added explanation in the configuration documentation regarding the impact of the `add_timestamps_use_datetime` setting on the schema table
- Updated the comments for `addTimestampsUseDateTime` in the FeatureFlags class to clarify its effect on the schema table
- Ensured consistency between the documentation and code comments

Author: qnnp-me

docs/en/configuration.rst

@@ -562,7 +562,8 @@ For some breaking changes, Phinx offers a way to opt-out of new behavior. The fo
 * ``column_null_default``: Should Phinx create columns as null by default? (default: ``true``)
 
 Since MySQL ``TIMESTAMP`` fields do not support dates past 2038-01-19, you have the option to use ``DATETIME`` field
-types for fields created by the ``addTimestamps()`` function:
+types for fields created by the ``addTimestamps()`` function. This setting also affects the start_time and end_time 
+columns in the schema table:
 
 * ``add_timestamps_use_datetime``: Should Phinx create created_at and updated_at fields as datetime? (default: ``false``)
 

src/Phinx/Config/FeatureFlags.php

@@ -24,6 +24,7 @@ class FeatureFlags
     public static bool $columnNullDefault = true;
     /**
      * @var bool Should Phinx create datetime columns for addTimestamps instead of timestamp?
+     * Also affects start_time and end_time column types in schema table.
      */
     public static bool $addTimestampsUseDateTime = false;