Stats: Enable tab switching for unsupported fields of hourly views

[dognose24]

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

Proposed Changes

• Restore chart tab switching for tab Visitors, Likes, and Comments.
• Use NULL to recognize unsupported Stats visits fields for hourly views to apply alternative data.

Why are these changes being made?

• Making unsupported hourly views tabs clickable with dedicated text in an empty state would communicate better to users. Context: Stats: Release new date filtering to production #97060 (comment).

Testing Instructions

• Apply Diff D167991-code and sandbox public-api.wordpress.com.
• Navigate to Stats > Traffic with the feature flag: ?flags=stats/new-date-filtering.
• Click on any day on the chart to navigate to the hourly views.
• Ensure the Views tab works as previously.

• Ensure the Visitors, Likes, and Comments tabs are clickable.
• Click on the Visitors tab.
• Ensure the chart is showing empty state with hourly views dedicated texts.
• Ensure the chart tab still displays the cumulative number of visitors for a single day.

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:commit-425f243de1a00631e999bd8dd22799fad73d1cac

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-425f243de1a00631e999bd8dd22799fad73d1cac&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-425f243de1a00631e999bd8dd22799fad73d1cac&env=a8c-for-agencies

[matticbot]

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

Sections (~52 bytes added 📈 [gzipped])

name   parsed_size           gzip_size
stats       +101 B  (+0.0%)      +52 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 (~11 bytes removed 📉 [gzipped])

name                              parsed_size           gzip_size
async-load-store-app-store-stats        -37 B  (-0.0%)      -11 B  (-0.0%)

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]

isFinite( null ) === true
Number.isFinite( null ) === false

[kangzj]

Hmmmm that's why we love JavaScript right? 🥲

[kangzj]

LGTM 🚀

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17054550

Some locales (Hebrew) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @dognose24 for including a screenshot in the description! This is really helpful for our translators.