Possible Misconfiguration of the Access Tests on Build

[ZAdamMac]

Describe the bug
Access tests during a regular or --inc run of the backup build process will throw an error if write permission is not present on a target file. To my understanding write permission is not required for the backup process and perhaps this should be adjusted

To Reproduce
Steps to reproduce the behavior:

1. Create a file in an acceptable target directory without write permissions to that file.
2. Run Tapestry, with a config that would attempt to back up the target directory.
3. Observe error in console output or logs; backup will continue unabated but the unwriteable file will be excluded from the backup.

Expected behavior
The file should be included if at all possible.

Log/Console Output
Error accessing /home/patches/roms/gbc/tetris.gbc: AccessTestResult(exist=True, read=True, write=False, execute=None). Verify it exists and you have permissions

Desktop (please complete the following information):

• OS: Ubuntu 20.04.5 LTS
• Version: 2.1.1

Additional context
This is one of several flaws exposed during recent production use of Tapestry, all alike. It's a minor fix, but ideally will be fixed in a release including all such flaws, or at least as many as require minor fixes.

[ZAdamMac]

This is going to be corrected in 2.2.2; a code change to build_ops_list is already made and being tested.