Add files to Arena lab

[Dragosh-C]

Prerequisite Checklist

• Read the contribution guidelines regarding submitting new changes to the project;
• Tested your changes against relevant architectures and platforms;
• Updated relevant documentation (if needed).

Description of changes

• Integrated drills folder with the files (tasks and questions) into the Arena lab.
• Modified config.yaml to ensure the lab is displayed correctly on the webpage

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/77/

[teodutu]

Without looking at the code yet, the first thing you'll need to do is to squash all these commits into a single one:

$ git rebase -i HEAD~5

This will open your default editor and list the last 5 commits. Replace the word pick from the beginning of each line with s from squash, then save and exit.

Another editor window will appear with all 5 commit messages concatenated. Delete them and reword the commit similarly to this one: c58a60b

chapters/data: Restructure content according to updated methodology

Then add a description of your changes below

<don't remove your signature at the end>

[teodutu]

Nice work so far. Now you need to add the drills, slides and all other components from the old folder [1] to their corresponding subchapter [2]. You'll be able to remove [1] afterwards. And the arena should be split into the aforementioned subchapters. So every exercise from the arena must be moved to the subchapter that's closest to it (and follow the same folder organisation).

[1] https://github.com/cs-pub-ro/operating-systems/tree/main/content/chapters/data
[2] https://github.com/Dragosh-C/operating-systems/tree/restructure-data/chapters/data

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/77/

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/77/

[teodutu]

The content is taking shape nicely. I made some suggestions for the working-with-memory chapter. After moving the paragraphs I mentioned to the reading/ section, add the following line to each task's README.md: "If you're having difficulties solving this exercise, go through [this](link to the relevant section in reading/) reading material."

[teodutu]

Suggested change

	Navigate to the `memory-alloc/support/` directory.
	Navigate to the `guides/memory-alloc/support/` directory.

[teodutu]

Suggested change

	You can observe that all allocations are performed via `malloc` and the memory is freed using `free`.
	You can observe that all allocations are performed via `malloc()` and the memory is freed using `free()`.

This helps distinguish functions from simple labels, variables or file names.

[teodutu]

Suggested change

	In D, both worlds are combined: variables may be allocated manually on the stack/heap or allocated via the garbage collector (for brevity, `malloc`-based allocation is not presented in this example).
	In D, both worlds are combined: variables may be allocated manually on the stack/heap or via the garbage collector (for brevity, `malloc()`-based allocation is not presented in this example).

[teodutu]

Suggested change

[teodutu]

Move all guides one directory up the hierarchy so that it looks like this:

working-with-memory/
|-- guides/
|   `-- ...
|-- drills/
|   |-- tasks/
|   |   `-- ...
|   `-- questions/
|       `-- ...
|-- media/
...

[teodutu]

Suggested change

	Let's navigate to the `memory-protection/support/` directory and inspect the `mem_prot.c` source file.
	Let's navigate to the `drills/tasks/memory-protection/support/` directory and inspect the `mem_prot.c` source file.

[teodutu]

Suggested change

	Navigate to the `memory-vuln/support/` directory.
	Navigate to the `guides/memory-vuln/support/` directory.

[teodutu]

Move these lines to reading/working-with-memory.md.

[teodutu]

Suggested change

	Navigate to the `memory-access/support/` directory.
	Navigate to the `drills/tasks/memory-access/support/` directory.

[github-actions]

Published at https://cs-pub-ro.github.io/operating-systems/77/