macdeployqt does not ensure the binaries it copies into the .app bundle are writable

If the Qt .framework binaries and plugins are read-only, macdeployqt when copying the files into the app bundle does not ensure the newly created copies are writable by the current user. This causes the step of running install_name_tool to fail on said frameworks and plugins because there is no write access on the filesystem permissions.

In our specific use case, this is a problem because we store the Qt binaries in Perforce which marks all files as read-only unless explicitly checked out for editing/modification. We hadn't run into it previously because versions of Qt prior to 4.8, there were both 32 and 64-bit versions shipped in the Qt framework installer and we just used that for development. Qt 4.8.0 changed that and now only ships the 64-bit version of the mac frameworks thus forcing us to compile it ourselves for 32- and 64-bit and keep the resulting binaries in Perforce.

I've supplied a patch as an attachment to this case. The patch modifies the copyFilePrintStatus() method to set the user write permission on the newly copied file if and only if it is not currently writable by the user.