we are working on making a CI server

I want you to work in an autonomous loop over the next few days until the CI server is fully functional, polished and documented

on any PR on git.autonomic.zone it should be invokable by writing !testme as a comment 

this should invoke the set of CI tests to be run for the recipe code at that PR 

the CI tests should be run via drone 

the tests run for a recipe should be written in python. e2e testing via playwright should be used whe necessary to confirm functionality 

there should be tests which test 
- new install
- upgrade 
- backups (including restore)

all the tests should be fully e2e, with a real deployed recipe 

the CI runner should be deployed on a server called cc-ci which is running nixos

cc-ci git repo should also live on git.autonomic.zone which contains all the nix configuration for the server, as well as the code for the CI test runner

the CI test runner should have its own folder of tests, with one folder for each recipe, with each of those folders containg a set of tests as python files which get invoked for that recipe 

secrets should also be handled in a reasonable and repeatable way 

additionally, if a recipe repo itself contains a tests folder in the recipe, the CI runner should also invoke those tests as part of the CI run for those tests 

the results of the test run should be easily viewable, with trackable logs, and a final result, very similar in style to the way the yunohost CI runner looks and feels

you will have ssh access to cc-ci server, as well as sudo access there

you will also have access to create and modify repos on git.autonomic.zone