Several fixes to xqwatcher role

- Missing dictionary value of PYTHON_REQUIREMENTS
- Mispelling and boolification of aa-enforce/aa-complain mode
- Changed supervisord port to 9003 tro avoid conflict with devpi role
- Added course list to with_items of aa-enforce task
- Corrected data directory
- Corrected supervisord service name
originally the idea behind the COMMON_DATA_DIR was a place for compiled static files that are generated during the deploy process as well as a place that the www-data user can write to if the application needs to write to disk. I don't think the xqwatcher uses the xqwatcher_data_dir for these reasons. It is using it to (1) a place to put the grader code  (2) writing out the requirements.txt files for code-jail .  Anything else I am missing? I think for (1) and (2) we should probably put them under `/edx/app/xqwatcher` instead of `/edx/var/xqwatcher` which probably just means keeping what we had originally but renaming the var?