Move the `tw_gcalSync` clone into a separate folder named `repository` in folder `gCal`.

Currently files belonging to the tw_gcal_sync repository modifications are put inside maintenance, because the gCal folder needs to be empty when the repository is cloned into it. Then they are moved into /gcal/taskw_gcal_sync after the repository is cloned. If there is a separate folder named repository made inside folder gCal, then askSync.sh

,insertCode.sh,customLocalServer.py can be copied into gCal which generates less clutter inside folder maintenance.

Moving askSync has an effect on the automated url opening, as some of the comands to get the url (e.g. insertCode or .. inherit the current/working directory in which the askSync is located.) *This most likely also holds for the first sync command in AskSync."

Start by tracing how gCal is cloned and how askSync.sh, insertCode.sh, and customLocalServer.py resolve their working directory. Move the clone into gCal/repository and verify that the sync commands and automated URL opening still work from their new locations without relying on the old maintenance layout.

Written by the indexing model from the issue text.