#23 Removed trimRange usage

[oleksandr-danylchenko]

Issue

This PR covers the issue #66. Where I expressed my doubts about whether we need a trimRange in the selection range processing flow. Two main points that shifted me towards the "No" answer are:

1. User can intentionally select non-textual nodes. Taking them out of the selection range only when they are at the edges, but not in the middle, seems like a partial prevention of a behavior
2. Ranges that have the start/endContainer.nodeType different from the Node.TEXT_NODE still can contain only the textual annotatable content. And such ranges are usually created when using the .setStartAfter/. setEndBefore

But to grasp the whole picture you can get acquainted with the detailed description and thought process here - #66 (comment)

[rsimon]

The trimRange function is really a remnant of the previous version of the text annotator or, in fact, even the previous version's predecessor (which worked in a "controlled environment" of a single DIV). Back then, the goal was simply to remove trailing and leading spaces.

I extended it later so that highlight SPANs would get inserted only across the text nodes. But, obviously, that was a very different rendering approach back then.

I'll review this PR when I have the time, but I believe trimRange is indeed not needed any more.

[oleksandr-danylchenko]

Thank you very much for the feedback 🙏🏻
The doubts of me just using the library in some unintended way were tearing me apart. And another portion of doubts aobut submitting such a PR would be considered as a super bold move 😅