Add shared empty-state and error-state components

[Chucks1093]

Summary

Add shared empty-state and error-state components for marketplace screens.

Context

Contributors will need consistent UI states as creator listings, profiles, and holdings pages are added.

Scope

• Create reusable empty-state and error-state components
• Support cases like no creators, no holdings, and failed data loads
• Keep the components accessible and consistent with the current branding

Acceptance Criteria

• Shared empty and error components exist in the client repo
• At least one page demonstrates their usage
• Components are documented well enough for reuse in future issues

[Chucks1093]

Closing this for now because the current Wave submission is focused on the server and contracts repositories. For updates or extra context, reach out in our Telegram channel: https://t.me/accesslayerorg