Is the `code` directory necessary?

[ckipp01]

When using cmtc and you unzip the course you end up with the following structure:

.cmt
code

Especially for Scala and Metals users it's a problem if they don't actually open up code as the root of the workspace. If they don't Metals won't work as expected. One way to avoid that is to gently push users to open code, however having the .cmt dir here makes it seem like maybe this is the root. Is there a reason to have the code dir? Instead could the .cmt dir just be in the root of the actual code dir? This might avoid any confusion and get rid of an arbitrary extra dir.

[eloots]

The idea of the code folder is to reserve it exclusively for exercise code. Right now, the root folder only holds the course metadata (.cmt folder), but if one decides to distribute other stuff as part of the student's course artefact like for example a slide deck in PDF format or some docker-compose files, they would reside in the root folder (or a subfolder thereof such as slides or docker).
Right now, adding such extra files or folders is a manual process (post generation of the student course artefact using cmta studentify, but one can imagine this being done automatically (via configuration).