Wrapped bemto block's modifiers are treated as block-starting

[kizu]

Test case:

test('with a wrapped component', () => {
  const wrappedComponent = bemto('.wrappedComponent');
  testSnapshot(
    bemto(wrappedComponent),
    {
      className: 'newClassname',
      _mod: 'value'
    }
  );
});

Right now this would output:

exports[`with a wrapped component 1`] = `
<div
  className="newClassname newClassname_mod_value wrappedComponent newClassname_mod_value newClassname_mod_value_mod_value wrappedComponent_mod_value"
/>
`;

That's not that trivial to fix, as we can't tell just from the classNames alone that they're added by bemto. So when we pass a one bemto block to another, we don't have a way to tell which classes should be treated as block-starting.

[kizu]

That seems to be fixed, not perfectly, but better than nothing I guess, I'll need to investigate nested blocks more

[kizu]

Prevented some of the cases from happening, but still not perfect and could potentially prevent for some valid stuff from being created.

For now, the best show would be if it would be possible to store the names in the context, not sure if this would be viable though.