[Dynamic Dashboard] Improvements to the custom range selection logic

[hichamboushaba]

Closes: #11509

Description

This PR fixes the logic of the custom range in the top performers card, the logic is as follows now:
When selecting the custom ranges dropdown entry, if a custom range has already been saved, it will be used directly; otherwise, the date picker will be shown.

The PR also fixes an issue where dismissing the date picker would not cancel the change to the "Custom Range" entry.

Testing instructions

1. Clear the app's data for the following steps (you can alternatively remove the datastore files from the storage).
2. Open the app.
3. In the performance card, tap on the range button.
4. Select "Custom Range"
5. Confirm the date picker is shown.
6. Dismiss it.
7. Confirm the range didn't change.
8. Re-select "Custom Range"
9. Choose a range in the date picker.
10. Confirm the range was updated.
11. Switch to a different range.
12. Switch to the "Custom range"
13. Confirm the previous range is applied automatically.
14. Repeat 3 to 13 for the top performers card.

Images/gif

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Flavor	Jalapeno
	Build Type	Debug
	Commit	ec699ee
	Direct Download	woocommerce-prototype-build-pr11510-ec699ee.apk

[hichamboushaba]

This renaming was done just for consistency, the term granularity doesn't apply to tabs anymore after introducing the custom range.

[hichamboushaba]

The LiveData here wasn't observed anywhere, which means it always had the value as null, and it caused a bug where opening the date picker doesn't show the current custom range.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 2.32558% with 42 lines in your changes are missing coverage. Please review.

Project coverage is 40.82%. Comparing base (5ed1a5c) to head (ec699ee).
Report is 2 commits behind head on trunk.

Files	Patch %	Lines
...d/topperformers/DashboardTopPerformersViewModel.kt	0.00%	23 Missing ⚠️
.../topperformers/DashboardTopPerformersWidgetCard.kt	0.00%	11 Missing ⚠️
...roid/ui/dashboard/stats/DashboardStatsViewModel.kt	20.00%	3 Missing and 1 partial ⚠️
.../kotlin/com/woocommerce/android/AppPrefsWrapper.kt	0.00%	2 Missing ⚠️
...rc/main/kotlin/com/woocommerce/android/AppPrefs.kt	0.00%	1 Missing ⚠️
...ashboard/stats/GetSelectedRangeForTopPerformers.kt	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##              trunk   #11510      +/-   ##
============================================
- Coverage     40.83%   40.82%   -0.02%     
  Complexity     5180     5180              
============================================
  Files          1070     1070              
  Lines         62310    62327      +17     
  Branches       8499     8502       +3     
============================================
  Hits          25444    25444              
- Misses        34578    34595      +17     
  Partials       2288     2288              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[0nko]

Looking good 👍

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ Resources$NotFoundException: String resource ID #0x0 Dashboard View Issue
• ‼️ IndexOutOfBoundsException: Index 2 out of bounds for length 2 com.woocommerce.android.util.DateUtils in getLo... View Issue
• ‼️ IndexOutOfBoundsException: Index 2 out of bounds for length 2 com.woocommerce.android.util.DateUtils in getSh... View Issue
• ‼️ ArrayIndexOutOfBoundsException: length=12; index=19 Dashboard View Issue
• ‼️ NumberFormatException: For input string: "20 14" com.woocommerce.android.util.DateUtils in getLo... View Issue

_{Did you find this useful? React with a 👍 or 👎}