Refactor (and delete?) the src/mixins/base-input.js::change() method

[volterra79]

Checklist

• I've searched through the current issues to make sure this feature hasn't been requested already.

Motivation

There is a lot of confusion about input change of state.value fields (form's input).

It can be changed by input itself or in some other way (eg. result of default_expression).

Suggested solution

Remove change (mixin base-input) method:

g3w-client/src/mixins/base-input.js

Lines 36 to 44 in 9118100

	// called when input value change
	change() {
	this.service.setEmpty();
	this.service.setUpdate();
	// validate input if is required or need to be unique
	if (this.state.validate.required || this.state.validate.unique) this.service.validate();
	// emit change input
	this.$emit('changeinput', this.state);
	},

in favor of a common state.value watcher (or another way).

Alternatives considered

No response

[Raruto]

I know it's a much broader topic, but I'm also of the opinion that some classes and functions (in here) could be moved directly into the editing plugin.

If then in the future some similar features will be necessary within other plugins (eg. editing some of the layer properties), it would be safier to re-implement that functionality within each "external" plugin (or that at least that this third party plugin should relies mostly on classes provided by the editing plugin, and not somewhere in between) .

[volterra79]

@Raruto I agree. It is just a remainder to don't forget to refactor editing in better way