Updates to booking flow

[sorokinvj]

• create a BookingStepsManager that will manage booking steps with "back" functionality and saved answers
• create a Progress component, that will show how much progress has been made so far by user
• create 3.2 Create “Guest selector” step
• re-build Select dates screen, include it in booking steps, change styles according to new design
• create Accommodation step
• update Questionnaire step according to new design
• create a Checkout step
• update/create Success step
• update Volunteering step according to new design

Design

[sorokinvj]

@closerearth Questions:

1. Did I understand correctly that the new Booking flow is the same for both guests and members, I am asking about the set of screens and elements on them - from what I see now probably $TDF payments are available only for members? so the TDF <> FIAT switch on the checkout will be only for Members?
2. Will we need any new backend endpoints to achieve the task?
3. Are there any limitations for Guests selector screen? Maximum number? Do we need to fetch any data here?
4. How do I get available accomodations on "Select accomodation" screen? is it just platform.listing.find() as in current pages/listings/index.js? Do I need to select just listingId to make a final call on the checkout?
5. Do we need to change api.post('/payment', {}) and setBooking({ ...booking, status: 'confirmed' }) with the new checkout? Will backend expect any new info like listingId?
6. What about the desktop layout? Do we need them or just some general rules while adopting?