Excluding the plugin from aggregation in combination with calls to Drupal.t() seems to break things under certain circumstances. Core plugins that use Drupal.t() inside their JS are not exlcuded from aggregation, for example internal.drupal.ckeditor5.image.
Unfortunately I can't provide exact steps here, but I think it's good enough to do what core does in this situation, I don't see anything speaking against including the JS in aggregation, I could be missing something though.
Include the plugin JS in aggregation by changing the library definition.
Active
2.0
Code
I have a similar issue on one of my projects, some users have JS errors related to Drupal.AjaxCommands.prototype.
Applying the change fixed the issue.