Interactivity: Warn texts should be eliminated from production builds

[sirreal]

Flagging that all warning messages end up being included in the production bundle when using the warn util. They are never printed on production because the body of the helper method goes through the tree-shaking step.

@wordpress/warning package uses this Babel plugin: https://github.com/WordPress/gutenberg/blob/trunk/packages/warning/babel-plugin.js to ensure that all usage also gets automatically wrapped with the check against SCRIPT_DEBUG, similar to how it is implemented in the util.

Originally posted by @gziolo in #61409 (comment)

[sirreal]

If we come up with a more unique name that's unlikely to collide, we could remove this via terser with the following option and not require the babel transform.

This is an idea, not a recommendation.

{
  compress: {
    pure_funcs: ['warn']
  },
}