Add 'Document->Clone' menu command

This copies the current document text and properties into a new
document, similar to the old Save As 'Open file in a new tab'
option, but easier to understand and decoupled from saving.

One notable difference is that the new document does not copy the
filename - the old behaviour was confusing and error-prone for the
user (e.g. editing two documents with the same filename).
Disable 'Save As' dialog Rename button unless document exists on disk
Mark cloned documents as modified

This helps avoid accidental data loss.
Clone line breaking, auto indent, indent type, indent width settings
Update manual for Document->Clone command
Copy selected text only (when present) for Document->Clone
Merge branch 'document-clone'
Add 'Move Line(s)' menu items in Edit->Commands (and popup menu)

Although using menu items for these is not very practical, it helps
discoverability, and they're more useful and intuitive than 'Transpose
Current Line'.
Ignore D angle brackets e.g. Foo!(x < 2)
Show Find in Files status summary on Windows
Reduce unnecessary redraws when typing
Fix clashing button mnemonic in detect/reload dialog (#3587465)
Fix a typo in the docs
Fix file saving behavior with "allow_always_save"

This preference should only be used for UI action, not for other file
saving triggering.
Properly register the statusbar context ID

Getting the statusbar context ID using the context registration API
allows for other (namely, plugins) to register their own context
without a risk of overriding Geany's one.
Update po/he.po
VTE: Grab focus upon middle click

When pasting with the X primary clipboard (middle mouse button), the
user expects the focus to be grabbed by the widget receiving the data.

No idea why the VTE itself don't grab upon middle click, though.
Python tag parser: fix detection of keywords followed by a tab (\t)

The Python tag parser used to require a space, and a space only, as the
character following a keyword.  Fix this so it allows any whitespace.
Merge pull request #82 from YosefOr/patch-5

Update po/he.po
Fix return value of search_find_text() when the match is out of bounds

When performing a regular expression search on a range, and there is a
match past the end of the range, search_find_text() used to improperly
return the position of the match, but without filling the
Sci_TextToFind structure.  This lead to the calling code assume there
was a match, and maybe read the uninitialized fields in the
Sci_TextToFind structure, thus leading to undefined behavior.

So, fix search_find_text() so it properly returns -1 when there is a
match but it is outside the bounds.