fix: AlertReportCronScheduler tests

[diegomedina248]

SUMMARY

Tests for the AlertReportCronScheduler component were skipped when the component was rewritten.
This PR introduces tests for the component using the react testing library, plus some optimizations in the component.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

None (other than the test execution results)

TESTING INSTRUCTIONS

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 #19288 (e3a790c) into master (1b4d8dd) will increase coverage by 0.00%.
The diff coverage is 83.33%.

❗ Current head e3a790c differs from pull request most recent head 380abe3. Consider uploading reports for the commit 380abe3 to get more accurate results

@@           Coverage Diff           @@
##           master   #19288   +/-   ##
=======================================
  Coverage   66.59%   66.60%           
=======================================
  Files        1682     1682           
  Lines       64314    64317    +3     
  Branches     6559     6559           
=======================================
+ Hits        42832    42837    +5     
+ Misses      19781    19779    -2     
  Partials     1701     1701           

Flag	Coverage Δ
javascript	51.37% <83.33%> (+0.01%)	⬆️

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

Impacted Files	Coverage Δ
...CRUD/alert/components/AlertReportCronScheduler.tsx	87.50% <83.33%> (+10.57%)	⬆️
...-frontend/src/components/CronPicker/CronPicker.tsx	100.00% <0.00%> (+14.28%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b4d8dd...380abe3. Read the comment docs.

[rusackas]

@eschutho would love to get feedback from someone closer to this feature, in case there's any risk I'm not spotting here.

[eschutho]

@diegomedina248 do you think we need useCallback for simple Input component props?

[diegomedina248]

It doesn't hurt nor improve in this case, but I believe it's cleaner

[eschutho]

It's a bit more code and a bit more computation imo, which is my only concern with not much performance impact, but it's not a big deal. I'll cc @rusackas if he has any opinions.

[eschutho]

but to your comment of it being cleaner, @diegomedina248 I meant to also ask in what way?

[eschutho]

@eschutho would love to get feedback from someone closer to this feature, in case there's any risk I'm not spotting here.

Looks great.. thanks for the tests @diegomedina248!