Error state for card component

Description

When people are using the card component to display data on a dashboard, there may be occasions when we're not able to fetch the data that's meant to be displayed. In these scenarios, it would be nice to have an error state that's contained within the card, so we don't have to rely on alerts, which can be more obtrusive/disruptive, especially when multiple alerts appear on a page.

Figma file

View design specs in Figma →

Checklist

Make sure the following are completed before closing the issue:

1. Assign the correct component label to this issue.
2. Create an MR with the additions or updates needed.
3. Be sure to get your MR reviewed by a FE/UX Foundations designer.
4. When applicable, create an MR in Pajamas to update the demos. If you do not have capacity to complete the demos, create an issue in Pajamas and bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one.
5. When applicable, create an MR in Pajamas to update the component status.
6. When applicable, create an issue in Pajamas using the "Component Documentation" issue template to update guidelines. Ping a designer on your team for awareness and bring the issue to your team planning meeting for prioritization and scheduling.
7. When applicable, create an issue in Pajamas using the "Figma update" issue template to update the Figma UI Kit. Ping a designer on your team for awareness and bring the issue to your team planning meeting for prioritization and scheduling.
8. When introducing a major or breaking change, communicate the changes within the Engineering Week in Review.
9. 🎉 Congrats, you made it! You can now close this issue.