Add the "Dev" changelog section

[m1r0]

Proposed Changes

• Add the "Dev" section to the changelog.
• Add more detailed descriptions of each change log section.
• Fix the editorconfig for the composer.json file so it uses tabs instead of spaces.

Testing Instructions

1. Run npm run changelog.
2. For the change significance step, select one of patch/minor/major.
3. In the type of change step, make sure there is a dev section.

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 #6804 (f2583a2) into trunk (c1a9bb1) will increase coverage by 0.01%.
Report is 51 commits behind head on trunk.
The diff coverage is 79.94%.

@@             Coverage Diff              @@
##              trunk    #6804      +/-   ##
============================================
+ Coverage     49.32%   49.33%   +0.01%     
- Complexity    10538    10539       +1     
============================================
  Files           575      575              
  Lines         44501    44503       +2     
  Branches        402      402              
============================================
+ Hits          21950    21956       +6     
+ Misses        22224    22220       -4     
  Partials        327      327              

Files Changed	Coverage Δ
includes/class-sensei.php	23.41% <0.00%> (ø)
...al/student-progress/tools/class-migration-tool.php	31.03% <31.03%> (ø)
...er/migrations/class-student-progress-migration.php	80.89% <80.89%> (ø)
...ncludes/blocks/class-sensei-block-view-results.php	74.28% <100.00%> (ø)
includes/class-sensei-settings-api.php	15.47% <100.00%> (ø)
includes/class-sensei-settings.php	70.70% <100.00%> (ø)
includes/internal/emails/class-email-sender.php	99.02% <100.00%> (ø)
...ludes/internal/emails/class-email-settings-tab.php	85.82% <100.00%> (ø)

... and 1 file with indirect coverage changes

---

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 6585162...f2583a2. Read the comment docs.

[donnapep]

In a team meeting, we decided to tweak this PR to add more detailed descriptions of each change log option, and pair it with a P2 post to explain proper change log entry usage.

[m1r0]

I've updated the descriptions in 988184c. LMKWYT. 🙂

[m1r0]

@donnapep I would like to know if the examples in the descriptions are making sense to you. If not, the future explainer P2 post might have to be in a more detailed format.

[donnapep]

Looks good! Hope you don't mind, but I tweaked it slightly in f2583a2, and changed one of the descriptions to include template changes for the dev option.

[m1r0]

Looks even better, thanks!