BUG: Trait add/remove can fail because collection type is inconsistent

GrapesJS version

• I confirm to use the latest version of GrapesJS

What browser are you using?

Brave Version 1.31.88 Chromium: 95.0.4638.69 (Official Build) (64-bit) on Linux

Reproducible demo link

https://jsfiddle.net/0a3o7cL6/

Describe the bug

Methods which operate on a component's trait collection (e.g. addTrait and removeTrait) seem to always assume the collection will be the Backbone-derived collection type, however there are cases where it's a simple Array instead. The code then attempts to call methods which don't exist.

I'm not familiar enough with the codebase to say for certain whether the actual bug is get('traits') returning the inconsistent type or the calling methods not accounting for the mixed return type. I discovered this behavior in the Video component, which has its runtime trait overwriting, I'm unsure if any other components are affected.

The JSFiddle is basically taken from: https://github.com/artf/grapesjs/issues/1999

How to reproduce the bug?

1. Add a call which adds a trait to a component (in init or another callback) which has an unreliable trait collection type (Video confirmed)
2. Attempt to create an instance of that component

What is the expected behavior? addTrait should not explode

What is the current behavior? Uncaught TypeError: this.get(...).add is not a function

Code of Conduct

• I agree to follow this project's Code of Conduct