Hiding dashboard cards: add empty state view

[kean]

Related issue: #20296

Previous PRs (dependencies):

1. Hiding dashboard cards: generalize logic for storing preferences #20365
2. Hiding dashboard cards: add Personalize Home Tab screen #20369
3. Hiding dashboard cards: add context menus #20384

There is only one commit in this PR: fb67fbd5.

Add an empty state view in case there are no cards to display on the Home tab.

To test:

• Hide all cards from the dashboard
• Verify that the new empty state view is displayed

Regression Notes

1. Potential unintended areas of impact
   n/a (new feature, doesn't affect the existing cards)

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   I performed manual testing

3. What automated tests I added (or what prevented me from doing so)
   I covered the new logic for displaying the empty state view with unit tests

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[kean]

I removed AppConfiguration.isJetpack from here to make it easier to test using the WordPress test target. I'm planning to add AppConfiguration.isJetpack check to FeatureFlags instead one we are ready to enable it, the same way it's done for prompts, for example:

case .bloggingPrompts:
    return AppConfiguration.isJetpack

[kean]

Other state views such as ghost and failure are also displayed using DashboardCard. I kept it consistent.

[osullivanchris]

How does the button look in dark mode? For the button background color I used 'fill color - tertiary' in the design. Which has a light mode and dark mode version. But realise I never specifically called that out.

[kean]

You can find the dark mode screenshot in the previous PR #20369.

[osullivanchris]

@kean ah cool, looks good thanks!

[staskus]

Thanks! LGTM 👍 Adapts well with dynamic type, dark/light mode, bigger screens, smaller screens, and different orientations.

I agree with using the cell to it consistent. Even though cards.isEmpty || cards.map(\.cardType) == [.personalize] such code is necessary, it looks like a special case to me compared to other cards.

[staskus]

@kean there're some conflicts. Let me know when you fix them, I will run CI and auto-merge this PR. Thanks!

[kean]

@kean there're some conflicts. Let me know when you fix them, I will run CI and auto-merge this PR. Thanks!

Thanks for the review - I fixed the conflicts.