Post-install script on Linux: delete OpenBoardUser.config file (avoids a crash if the config file comes from a version <= 1.10a3)

Presumably due to the change in how pen strokes were saved to file (commit
8ed2e245), pen strokes with pressure levels were badly saved. They were
converted to lines instead of polygons, meaning that every time a page
was saved or duplicated, the lines would look worse and worse -- and
artefacts would appear.

This should now be fixed.

(due to commit 9adc8991).

Fullscreening should now work as expected in OSX 10.9 and 10.10, with
one or multiple monitors.

- Linked necessary Windows SDK libraries
- Solved compilation errors upon including `wmsdk.h` or other Windows
SDK headers (`interface` keyword wasn't recognized)

Page DPI is now saved as the DPI that was read when opening the file.
While not a perfectly fool-proof fix, it will at least allow files to be
migrated between OB 1.02 and 1.10.

Note: the screenshot can only be taken on the primary display now
(rather than on the display in which the mouse is, as was the case
before).

Previously, duplication did not copy the transformation matrices of group
members correctly. This made grouped objects move away when saving and
re-opening a document.
This should now be fixed.

- Added an overload for setMatrix in UBGraphicsMediaItem, to propagate
  matrix changes to the child videoItem
- Upon loading a video, the child videoItem is now added correctly, and
  set to the right position

(Merge branch 'craig-dev' into dev)

Simply added copying of zValue to the deep copy functions. As tested on
OSX, this does pose any problems when duplicating an item on-page (i.e
generating a new item with a zValue equal to its original).

This reverts commit fb05343e.

The lines removed in this commit led to (presumably) unintended
behavior: when saving a document, pen strokes were saved not as a group,
but just as their constituent polygons.
This meant that the following block of code, that handles saving pen
strokes correctly, was never executed.

This doesn't fix the z-Value issue (#12), but it seems to be a step in the right
direction.