Merged in monorepo-step-1 (pull request #1080)

Migrate to a monorepo setup - step 1

* Move web to subfolder /apps/scandic-web

* Yarn + transitive deps

- Move to yarn
- design-system package removed for now since yarn doesn't
support the parameter for token (ie project currently broken)
- Add missing transitive dependencies as Yarn otherwise
prevents these imports
- VS Code doesn't pick up TS path aliases unless you open
/apps/scandic-web instead of root (will be fixed with monorepo)

* Pin framer-motion to temporarily fix typing issue

https://github.com/adobe/react-spectrum/issues/7494

* Pin zod to avoid typ error

There seems to have been a breaking change in the types
returned by zod where error is now returned as undefined
instead of missing in the type. We should just handle this
but to avoid merge conflicts just pin the dependency for
now.

* Pin react-intl version

Pin version of react-intl to avoid tiny type issue where formatMessage
does not accept a generic any more. This will be fixed in a future
commit, but to avoid merge conflicts just pin for now.

* Pin typescript version

Temporarily pin version as newer versions as stricter and results in
a type error. Will be fixed in future commit after merge.

* Setup workspaces

* Add design-system as a monorepo package

* Remove unused env var DESIGN_SYSTEM_ACCESS_TOKEN

* Fix husky for monorepo setup

* Update netlify.toml

* Add lint script to root package.json

* Add stub readme

* Fix react-intl formatMessage types

* Test netlify.toml in root

* Remove root toml

* Update netlify.toml publish path

* Remove package-lock.json

* Update build for branch/preview builds


Approved-by: Linus Flood

apps/scandic-web/app/[lang]/(live)/(public)/hotelreservation/README.md

@@ -0,0 +1,27 @@
+# Booking flow
+
+The booking flow is the user journey of booking one or more rooms at our
+hotels. Everything from choosing the date to payment and confirmation is
+part of the booking flow.
+
+## Booking widget
+
+On most of the pages on the website we have a booking widget. This is where
+the user starts the booking flow, by filling the form and submit. If they
+entered a city as the destination they will land on the select hotel page
+and if they entered a specific hotel they will land on the select rate page.
+
+## Select hotel
+
+Lists available hotels based on the search criteria. When the user selects
+a hotel they land on the select rate page.
+
+## Select rate, room, breakfast etc
+
+This is a page with an accordion like design, but every accordion is handled
+as its own page with its own URL.
+
+## State management
+
+The state, like search parameters and selected alternatives, is kept
+throughout the booking flow in the URL.