detach chromium from shell script PID when using brew provided wrapper

[fabio42]

This simple shell wrapper is provided to execute chromium from command line.
The way it is defined, chromium will have the PID /bin/sh as PPID:

  501 77821  1088   0  6:24pm ttys028    0:01.53 -zsh
  501 78177 77821   0  6:24pm ttys028    0:00.01 /bin/sh /usr/local/bin/chromium
  501 78181 78177   0  6:24pm ttys028    0:01.83 /Applications/Chromium.app/Contents/MacOS/Chromium

I'm using chromedp to interact with chromium/Chrome, and this
behaviour triggers some issues. When the execution context is done in
the library, it triggers the termination of the shell process instead of the chromium process and
chromium is left as an orphan process on the system.

There is an open issue documenting this behaviour here

Using exec will detach chomium process from the shell, and will provide
expected behaviour when called with such libraries; user
experience when calling chromium from the shell will not change.

  501 77821  1088   0  6:24pm ttys028    0:01.61 -zsh
  501 93092 77821   0  6:26pm ttys028    0:01.40 /Applications/Chromium.app/Contents/MacOS/Chromium

Thank you.

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

After making all changes to a cask, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask {{cask_file}} is error-free.
• brew style --fix {{cask_file}} reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused.
• Checked the cask is submitted to the correct repo.
• brew audit --new-cask {{cask_file}} worked successfully.
• brew install --cask {{cask_file}} worked successfully.
• brew uninstall --cask {{cask_file}} worked successfully.