form.field.Text: editable_ config

We now have a logic clash of the following 2 methods:

    afterSetEditable(value, oldValue) {
        const
            me      = this,
            { cls } = me;

        NeoArray.toggle(cls, 'neo-not-editable', !value);
        me.cls = cls
        me.changeInputElKey('readonly', value ? false : true);

        me.triggers?.forEach(trigger => {
            trigger.hidden = value ? true : trigger.getHiddenState?.() || false
        });
    }

    afterSetReadOnly(value, oldValue) {
        let me  = this,
            cls = me.cls;

        NeoArray[value ? 'add' : 'remove'](cls, 'neo-readonly');
        me.cls = cls;

        me.changeInputElKey('readonly', value ? value : null);

        me.triggers?.forEach(trigger => {
            trigger.hidden = value ? true : trigger.getHiddenState?.() || false
        })
    }

If a field has editable: false and readOnly: false, assuming that the editable config will get set first, the first method will hide the triggers and the second one will show them again.

We need a new method like updateTriggerVisibiliby() which honors the combination of both configs and gets called in both afterSet methods.

afterSetEditable() should not hide triggers by default though, so in case we remove the part in there, we don't need the new method.

I am still not sure, if applying readonly on DOM level is a smart idea for fields that a user has to fill. accessibility (screen readers) => confusing. Not sure if we can make a field work like it is readonly, without using the DOM attribute (just CSS).