Fix output not appearing in snippets which are not evaluated

[samuelfangjw]

Description

Fixes #1876

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Code quality improvements

How to test

For snippets which are not evaluated, output should be visible (if present). For example, the chapter 4.4.1, lives_near(list, "Reasoner"... should be visible, as seen in the screenshot below.

Checklist

• I have tested this code
• I have updated the documentation

[martin-henz]

I think we should always show the expected output, regardless whether the program is runnable or not.

[coveralls]

Pull Request Test Coverage Report for Build 1073781230

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.01%) to 29.719%

---

Totals
Change from base Build 1067179111:	0.01%
Covered Lines:	3164
Relevant Lines:	9780

---

💛 - Coveralls

[samuelfangjw]

I think we should always show the expected output, regardless whether the program is runnable or not.

This is already the case for all runnable program snippets that have <JAVASCRIPT_OUTPUT>, apologies if my initial comment was misleading.

I've taken this chance to also italicise <JAVASCRIPT_OUTPUT>, as per the specs, as well tweak the styles of code snippets very slightly so that snippets can be displayed without having to scroll horizontally on larger screens.

[martin-henz]

all good