Possibly drop the check for "is configuration changed"

[GitMensch]

As far as I see this function is only triggered by vscode and it is only triggered if a setting actually did change.

Is this the case? If yes then I'd remove the check from

vscode-overtype/src/configuration.ts

Line 45 in 9c89e69

// bail out if nothing changed

Primary reason: if more than one person adds/changes settings in the same time we'll get to merge conflicts (easy to solve but still) but most important: I think that's a possible braking part (if someone forgets to adds a setting) and especially: doesn't seems to be necessary (says the vscode-extension-noob).

Opinions? Insights?
OK for delete?