Hardcode CampusNet sysaccount in config yml for CN dumper

Config yml contains "user" and CampusNet ("CN") API specific "PAP" value, to retrieve participants list and rights/roles from CN.

Problem is that "user" can change, if course gets a new course instructor for a given semester, and that leaves the config yml for cn dumper non functional for that course. (It is a manual process to update the config yml file with new course instructor and it is cumbersome to create the PAP for said user). Furthermore sysadmins do not know if course instructors are replaced.

We propose that an already existing enote-test-account, for instance "enotema", is hardcoded in all created config yml files, with the never changing PAP value for that user.

"enotema" then just have to be added by the course instructor in his course in CN, for the CN dumper to work. This can also be done via a Arcanic (CN developer) made script, so that "enotema" is always added as hidden admin, to all Compute courses.

This idea, in general, should be expanded, so that minimal effort is required for a given course instructor, to initiate use of enote, for his course. In the perfect scenario, involvement of sysadmins for new courses are never needed.