`RPA.Windows` improvements

[mikahanninen]

• [x] https://github.com/robocorp/rpaframework/issues/797
• [x] https://github.com/robocorp/rpaframework/issues/796
• [x] https://github.com/robocorp/rpaframework/issues/791
• [x] https://github.com/robocorp/rpaframework/issues/704
• [x] https://github.com/robocorp/rpaframework/issues/591
• [x] https://github.com/robocorp/rpaframework/issues/483
• [x] https://github.com/robocorp/rpaframework/issues/820
• [x] Make PrintTree return as well: https://github.com/robocorp/rpaframework/issues/779
• [x] Check KeePass behaviour: https://github.com/robocorp/rpaframework/issues/806
• [x] @xylix Windows recording investigations: https://github.com/robocorp/rpaframework/pull/834
• [x] https://github.com/robocorp/rpaframework/issues/871

[cmin764]

Extra closed issue (can be re-opened): https://github.com/robocorp/rpaframework/issues/779

Just in case this epic will provide a solution for it as well.

[xylix]

834 added some error handling, but cases where user starts recording (python -m RPA.Windows or windows-record) if the first click is to desktop, there will be a weird error that makes the underlying library give out errors, and so for now the recording is aborted if this buggy behaviour happens.

But recording clicks on desktop works correctly if another application is clicked first. Unclear to me why initial clicks to desktop are so broken.