for-loops: Port "Bird Watcher" exercise from JS or C#

[ErikSchierboom]

This is part of our September Spring to get the Go Track in shape. Please read the Overview issue for more details. This exercise is claimed by @sachinmk27.

---

Before building this exercise, please read up on the documentation.

The goal of this exercise is to teach how to write a for loop, the different parts of the loop header, explain that there are no other loops in go than "for", break, continue, about should mention endless loops as pitfall

Copy/paste/modify the JS bird watcher exercise. This exercise will be teaching the for-loops concept.

The new exercise will have two prerequisites: numbers and conditionals-if.

---

#1380 can be closed once this is done.

[sachinmk27]

I'd like to work on this

[junedev]

@sachinmk27 Thanks! I assigned you. I recommend you first check out the JavaScript exercise and also the for-loops concept in the JavaScript track (introduction and about). You can probably re-use a lot from there.

Note that this exercise/concept should NOT include range. This is covered in another exercise later in the concept tree.

[jmrunkle]

FYI: this is blocking #1565, so please comment on that issue once this is implemented.

[ErikSchierboom]

@sachinmk27 And let us know when you have any questions, we're here to help.

[junedev]

@sachinmk27 The increment and decrement operator was introduced as part of "arithmetic operators" concept in the exercise that teaches numbers. That means you dont need to introduce it here anymore.

[ErikSchierboom]

@sachinmk27 Just out of curiosity: how is the porting going?

[sachinmk27]

Hi, have gone through the docs. Haven't been able to make time to implement it, hopefully should be done in the next couple of days. Is that okay?

[ErikSchierboom]

Yeah sure!

[jmrunkle]

@sachinmk27 - just checking in again since this is blocking one of my issues. As a note - it may be easier to work on if you break this down into a few smaller steps (rather than trying to do the full implementation at once). If the top level config.json has the status "wip" for this exercise it will not show up on the website (which can be useful for partial implementations). For example, you could check-in the initial file stubs without completing the whole exercise just to get the structure down and some of the initial metadata. Another way is to start is to leverage a draft PR so that you can start getting some initial feedback and suggestions if you are having any trouble getting it setup. Cheers!