Creeple - Basket management flows

I've been playing around with how to manage the basket functions and the micro-interactions inside the BasketList component (and by virtue, other places we may use lists in the future).

There are multiple userflows required to properly catch and communicate users may encounter including users wanting to:

1. Edit their basket items (in this case editing the customisation of an Avatar)

2. Delete the avatar from their basket

3. Download individual items (multiple item flow not displayed here)

4. Be notified of any rejection the API I've designed to export images might throw in it's response.

There's still a bit to do here, such as "what happens when an optimisitic UI update is interrupted and/or fails for any reason.