Fix event dispatch and input type handling for all HTML input types

This merge request adds test coverage for then resolves all the open issues and merge requests regarding input / change / keyboard events when using setValue() to populate an <input>, <textarea> or < contenteditable=true > element.

To build the testcase, rather than the approach taken in !134 (closed) I started by capturing the exact list of events fired by keyboard input from all of the W3C input types that provide a straightforward keyboard interface in Chrome 115.0.

Some of the fixes here replace merge requests that were already open, but I've taken a slightly different route to fixing the issues that made sense in the overall context of this branch.