Stats: Update to fix header consistency

[annacmc]

Related to https://github.com/Automattic/red-team/issues/271

Proposed Changes

• Ensure the days consistently show date ranges with exact dates

Why are these changes being made?

• To ensure header consistency for the Date Filtering for the Traffic Page project

Testing Instructions

• Open up the Calypso live branch
• Apply the stats/new-date-filtering flag
• Try different date ranges and selections, ensuring that the title continues to show the exact + correct date ranges
• Check other stats locations and triple check this doesn't affect anything else, anywhere else
• Select a full year date range (eg. 1st jan - 31st dec) and check that just the year is shown (eg. 2023)
• Select a full month date range (eg. 1st jan - 31st jan) and check that just the month + year is shown (eg. October 2024)
• Select a single day, and check just the date is showing (eg. November 22, 2024)

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-125415

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-125415&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-125415&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug updat/stats-fix-header-consisitency on your sandbox.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~108 bytes added 📈 [gzipped])

name   parsed_size           gzip_size
stats       +526 B  (+0.0%)     +108 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~104 bytes added 📈 [gzipped])

name                                       parsed_size           gzip_size
async-load-store-app-store-stats-listview       +514 B  (+0.2%)     +104 B  (+0.1%)
async-load-store-app-store-stats                +514 B  (+0.1%)     +104 B  (+0.1%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[dognose24]

Works as described!

[kangzj]

LGTM