feat: Style Corrections archive templates

[Takshil-Kunadia]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This pull request introduces styling enhancement to the correction archive templates to match the design shared.

Closes https://app.asana.com/0/1209292256643614/1209292256643623

Demo:-

Screen.Recording.2025-02-17.at.1.16.06.PM.mov

How to test the changes in this Pull Request:

1. Navigate to the corrections archive page.
2. Observe the layout and styling to ensure it aligns with the intended design specifications.
3. Verify that all elements are displayed correctly and that the page is responsive across different devices and screen sizes.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you successfully ran tests with your changes locally?

[Takshil-Kunadia]

@leogermani For the archive page description we can add a Customize setting, but we'll have to address #2435 (comment) before I add a setting for description.

[leogermani]

actually, the date and time should follow whichever format is set in the site Settings, so the Timezone name there should only be dislpayed if it's set to be displayed in the admin...

I think only working with the_date and _the_time should be fine here

[Takshil-Kunadia]

Ommitted the timezone from the heading.✅

[leogermani]

@thomasguillot can you have a look?

[thomasguillot]

It looks great, thank you @Takshil-Kunadia.

One thing that seems to be missing is the ability to control the number of corrections per page. Currently, it follows posts_per_page, which isn’t quite enough for this CPT’s archive page. Would it be possible to make this configurable via wp-config, such as: define( 'NEWSPACK_CORRECTIONS_PER_PAGE', 20 );... What do you think @leogermani?