Move job definitions into a dedicated "jobs" key in gitlab-ci.yml

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

I think it would be a better design decision to put all jobs in a dedicated jobs section in gitlab-ci.yml, for the following reasons:

• The need for considering some words as reserved is obviated, which not only poses naming limitations, but also is a threat to backward compatibility, if new root level options are going to be added in future.
• It just makes more sense! The first time someone sees image, cache, foo and bar in a file, they definitely are surprised to find out image and cache are configuration options but, foo and bar are two jobs!
• Readability is increased as number of jobs are increased, because it enforces all jobs to be grouped in one part of configuration, leaving other configurations separate from job definitions.