feat: update time comparison choices (again)

[john-bodley]

SUMMARY

Similar to #11294, this PR adds Y4Y time comparison choices to make it faster to compare with pre-pandemic times.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

CI.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[codecov]

Codecov Report

Merging #22458 (5cbd4b5) into master (858796b) will not change coverage.
The diff coverage is n/a.

❗ Current head 5cbd4b5 differs from pull request most recent head fde6335. Consider uploading reports for the commit fde6335 to get more accurate results

@@           Coverage Diff           @@
##           master   #22458   +/-   ##
=======================================
  Coverage   66.89%   66.89%           
=======================================
  Files        1850     1850           
  Lines       70701    70701           
  Branches     7750     7750           
=======================================
  Hits        47292    47292           
  Misses      21393    21393           
  Partials     2016     2016           

Flag	Coverage Δ
javascript	53.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...-chart-controls/src/sections/advancedAnalytics.tsx	14.28% <ø> (ø)
...legacy-plugin-chart-partition/src/controlPanel.tsx	25.00% <ø> (ø)
...gins/legacy-plugin-chart-rose/src/controlPanel.tsx	50.00% <ø> (ø)
...gins/legacy-preset-chart-nvd3/src/NVD3Controls.tsx	100.00% <ø> (ø)
...et-frontend/src/explore/controlPanels/sections.tsx	100.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[villebro]

LGTM. You may already know this, but freeform time comparisons are already supported:

I'm almost wondering if we should replace the current dropdown with a component similar to the time picker, as we don't really need the pre-populated values IMO.

[john-bodley]

@villebro I'm aware of that (and did communicate it to our users), though it seems like they still likely the idea of having it explicitly defined.