Restructure Output and Error Handling to be less of a wall of text

[illicitonion]

Currently https://github.com/CodeYourFuture/immersive-go-course/tree/main/projects/output-and-error-handling has a lot of up-front reading to do. This is putting some people off of getting through it, and also isn't great pedagogy.

Ideally we can restructure this so it's a bit more "read, do, read, do, read, do".

[SaadiaELF]

Or maybe we could split it up to two distinct parts :

1. Reading :

• Standard out and standard error
• Exit codes
• Handling errors in your code

2. Program in whole

Personally, I prefer to start by understanding the requirements of the program and then learn about what I need to create it.