Add student progress migration

[merkushin]

Resolves #5437

• This PR doesn't introduce a data migration mechanism. Only an interface for migrations and the migration for student progress comments.
• It doesn't work with transactions at this moment. We decided to consider them later.
• Only a very basic test added for the migration. Tests are WIP.

Proposed Changes

• Add a migration to copy status comments into custom tables.
• Add a tool to run migration manually.

Testing Instructions

1. Enable the feature: add_filter( 'sensei_feature_flag_tables_based_progress', '__return_true' );.
2. Go to Sensei LMS -> Tools.
3. Run Migrate comment-based progress.
4. You can run it several times. It processes 1000 comments per run.
5. If you see the message "Progress entries created based on comments: 0." it means there is nothing to migrate already.
6. To run it from the beginning you need to clean at least the option: DELETE FROM wp_options where option_name = 'sensei_migrated_progress_last_comment_id';
7. However, it won't insert duplicates, so you need to delete progress rows as well: TRUNCATE TABLE wp_sensei_lms_progress;

Pre-Merge Checklist

• PR title and description contain sufficient detail and accurately describe the changes
• Acceptance criteria is met
• Decisions are publicly documented
• Adheres to coding standards (PHP, JavaScript, CSS, HTML)
• All strings are translatable (without concatenation, handles plurals)
• Follows our naming conventions (P6rkRX-4oA-p2)
• Hooks (p6rkRX-1uS-p2) and functions are documented
• New UIs are responsive and use a mobile-first approach
• New UIs match the designs
• Different user privileges (admin, teacher, subscriber) are tested as appropriate
• Code is tested on the minimum supported PHP and WordPress versions
• User interface changes have been tested on the latest versions of Chrome, Firefox and Safari
• "Needs Documentation" label is added if this change requires updates to documentation
• Known issues are created as new GitHub issues

[codecov]

Codecov Report

Merging #7049 (d70ce71) into trunk (71616ad) will increase coverage by 0.16%.
Report is 2 commits behind head on trunk.
The diff coverage is 75.09%.

@@             Coverage Diff              @@
##              trunk    #7049      +/-   ##
============================================
+ Coverage     48.08%   48.25%   +0.16%     
- Complexity    10467    10534      +67     
============================================
  Files           573      575       +2     
  Lines         44164    44441     +277     
  Branches        402      402              
============================================
+ Hits          21235    21443     +208     
- Misses        22602    22671      +69     
  Partials        327      327              

Files Changed	Coverage Δ
includes/class-sensei.php	23.41% <0.00%> (-0.12%)	⬇️
...al/student-progress/tools/class-migration-tool.php	31.03% <31.03%> (ø)
...er/migrations/class-student-progress-migration.php	80.89% <80.89%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6738bcf...d70ce71. Read the comment docs.

[merkushin]

I want to leave this interface here as is.

[merkushin]

I want to move this class to includes/internal/student-progress/migrations.

[merkushin]

Didn't move yet, not sure.

[m1r0]

I didn't do in-depth testing but it worked great on what I've tested! I will do some more edge-case testing next week.

I remember you mentioning the handling of trashed comments. Is that part done or it will be in another PR?

[m1r0]

Did we plan to store dates in GMT for the new tables? If so, I don't think the comment_date is in GMT and might need some conversion. Maybe we can use comment_date_gmt instead?

[merkushin]

@m1r0 added usage of GMT date and conversion for the start date.

[m1r0]

Looks good. I wasn't able to find any issues. 🙂