GitLab

The 'master' branch name is confusing as it indicates some special branch name,
where it is actually just a 'ref'. 'branches' _is_ a special name as it
indicates 'all' branches.

Lets clarify the example a little to indicate this.
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>

The `note` alert box within the convdev doc was improperly formatted. 

We were emphasising a point that's no longer true since we implemented
deploy tokens in 11.0 so rationalize the docs here.

In the example response we have builds with status `success` but the
property `runner` is null, which is not a realistic representation of
the response. The runner is always sent if the build has ran.

closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53121

Fixes #56864

Also refactors and combines resources and examples.

Also refactors structure of the page
to make the first section more useful.

- Pipeline status
- Job running
- Rollback button

Until we solve https://gitlab.com/gitlab-com/gitlab-docs/issues/347,
let's just be explicit to avoid confusion.

Merge branch 'restrict-jupyter-login' of https://gitlab.com/amit1rrr/gitlab-ce into restrict-jupyter-login

- Move instructions to use project templates to getting started
- Move the fork illustration into the in-depth guide
- Add screenshot for current project templates

Copyedit - better wording

Copy edit - typo