Rework learning goals of each chapter

[uekerman]

Currently, the writing style we use for learning goals is not very consistent. For example, we take different perspectives (the students, we, no subject). Also we are not very explicit about details.

How to use git workflows to organize research software development in a team.

Could become

To organize research software development in a team, the students know the names and fundamentals of the most important git workflows and can chose and implement a suitable workflow for a given project.

Let's iterate over all leaning goals at once to clarify them better and to improve consistency.

[uekerman]

We also need to better distinguish between learning goals of a single lecture and learning goals of a complete chapter.

[uekerman]

• @IshaanDesai and @MakisH Improve learning goals as you go
• @IshaanDesai improve learning goals of the building and packaging chapter.
• @IshaanDesai improve learning goals of the testing chapter.
• @IshaanDesai, as you typically do the first lecture of every chapter: Update the learning goals of these intros. Don't only show those that are relevant for the Python part.
• Update learning goals of individual lectures.
• Finally, @uekerman, copy to website or remove this duplication of content.