feat: configuration options in create server

🔗 Linked issue

ES-411

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Added options to createServer which allows to customize the cors, cookieParser, and bodyParser middlewares

Context: The change is related to the hacky cors config customization which we've got atm in templates. Currently, the middleware app is run mostly on port 4000, because Storefront app occupies port 3000 (default port for Next.js), so I could change the origin to accept also localhost:4000, however there are also multistores which are run locally and other cases, when the current cors config is enough. The workaround which we do in the templates looks as follows

  const CORS_MIDDLEWARE_NAME = "corsMiddleware";

  const corsMiddleware = app._router.stack.find(
    (middleware: any) => middleware.name === CORS_MIDDLEWARE_NAME,
  );
  const multistoreUrls = listOfStoresDomains.map((storeUrl) => `https://${storeUrl}`);
  corsMiddleware.handle = cors({
    origin: [
      "https://dev.local",
      "http://localhost:3000",
      "http://localhost:3333",
      ...multistoreUrls,
    ],
    optionsSuccessStatus: 200,
    credentials: true,
  });

I propose to instead by default allow cors for all origins, and pass an option to configure it when calling createServer.

I've added also an option to pass config for cookieParser, and bodyParser, but I'm open to exclude it from this PR, because it extends our API layer.

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

vuestorefront / vue-storefront