Research & implement basket functionality

[nickdos]

As a proof of concept, add a simple "basket" functionality to the demo site.

Although a demo version can be developed that does not require user authentication, it probably makes sense to include that in the proof of concept. See #25.

Will have to decide where to store the user data. Initial implementation could simply use local storage but longer term, it should be stored in a backend service. 2 options I can think of are in userdetails (simple KV store via REST) or build a really simple API using S3 and API gateway (that could tie into the OIDC authentication, which also uses API gateway). Another option is AWS Amplify DataStore, which is tempting as one of the hosting options for the web component is Amplify. The downside is vendor lock-in. Here is an example shopping cart app.

Basic features:

• [x] "Add to basket" link on record page drawer
• [ ] "Add All to basket" link on species card view
• [x] Basket link in menu that shows the contents of a users basket
• [x] Create Basket view (drop-down or separate page??) with
• • [x] select one or more items
• • [x] remove selected items
• • [x] export selected items to Galaxy Australia

[nickdos]

Created feature branch issue-23.

[nickdos]

Done as MVP. Create a new issue for specific enhancements or bug fixes.