Add Bitwig+Chromaphone 3 as a hide_daw candidate

Under Bitwig, the plugin will crash when trying to enter text unless you
hide the DAW the plugin is being hosted under.

README.md

@@ -440,6 +440,10 @@ include:
 - **PSPaudioware** plugins with expandable GUIs, such as E27, may have their GUI
   appear in the wrong location after the GUI has been expanded. You can enable
   an alternative [editor hosting mode](#compatibility-options) to fix this.
+- When using recent _Applied Acoustics_ plugins like **Chromaphone 3** under
+  _Bitwig Studio_, text entry will cause the plugin to crash because Chromaphone
+  uses a different text entry method when it detects Bitwig. You can use the
+  `hide_daw` [compatibility option](#compatibility-options) to work around this.
 - The VST2 version of **SWAM Cello** has a bug where it asks the host for the
   current buffer's time and tempo information for every sample it processes
   instead of doing it only once per buffer, resulting in very bad performance.

src/common/utils.h

@@ -35,8 +35,8 @@ constexpr time_t audio_thread_priority_synchronization_interval = 10;
  * When the `hide_daw` compatibility option is enabled, we'll report this
  * instead of the actual DAW's name. This can be useful when plugins are
  * hardcoded to behave differently in certain DAWs, and when that different
- * behaviour causes issues under Wine. Examples of this are Melodyne 5 under
- * REAPER, and AAS Chromaphone 3 under Bitwig.
+ * behaviour causes issues under Wine. An example of such a plugin is AAS
+ * Chromaphone 3 when run under Bitwig.
  */
 constexpr char product_name_override[] = "Get yabridge'd";
 /**