Add "--no-open" to storybook-command to prevent errors when using ddev/docker

Problem/Motivation

When using kern_ux with ddev and trying to run the storybook-frontend inside of the ddev container, it fails with the following error:

/var/www/html/web/themes/contrib/kern_ux/node_modules/storybook/bin/index.cjs:23
  throw error;
  ^

Error: spawn xdg-open ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn xdg-open',
  path: 'xdg-open',
  spawnargs: [ 'http://localhost:6006/' ]
}

It seems to come from the fact, that the docker container running ddev does not know, how to open a browser.
To prevent the error, we can add the flag "--no-open" to the package.json's "storybook" command.

When people run the command, it gives a colored message with instructions on how to access the storybook, so I guess users won't be lost.

Steps to reproduce

Use kern_ux in a ddev-project and try to run the frontend build from inside the ddev container.

Proposed resolution

package.json

    "storybook": "storybook dev -p 6006 --no-open",

Remaining tasks

Review by team.

User interface changes

Browser doesn't open automatically when "storybook" command is run.
Error for ddev-users should be gone.