Add an option in settings to add arguments to the executable.

My plan was to use `--user-data-dir="/tmp/chrome_dev_test" --disable-web-security` to overcome some CORS issues and work on mind my frontend business, but I could not.

The issue names no files, tests, or entry points. Start by locating the settings definition and the executable launch path, then determine how configured arguments are represented and passed. Done means users can supply arguments such as the requested Chrome flags through settings.

Written by the indexing model from the issue text.