Fix crash when “close tabs” is sent to window with no tabs

It appears a window can hang around after its last tab has been closed. Such window receive notifications of items being deleted via the file browser, and will call the “close tabs” method in response to these, which does an out-of-range array access if no tabs exist.

The reason for why windows can hang around after last tab is closed has not yet been determined. It might be a retain cycle (bug) or a delayed release due to autorelease pools.

Fixes #1064
Improve application specific data in crash log

This makes it easier to automatically extract and index.
Dispose tree structure bottom-up to limit stack usage

With really long search strings, the recursive disposal of nodes would blow the stack
Add storage access info to crash reports
Checkin release notes
Upload via scp instead of pushing to GitHub