Use YAML 1.2 boolean values for generated log files

[itismadness]

The current log files are generated using values that are considered booleans under YAML 1.1, but not YAML 1.2.

This makes the generated logs use the standard boolean values of true/false instead of Yes/No so that the logs are parsed the same under both YAML 1.1 and 1.2 into booleans which is going to be less surprising to downstream automated consumers of these logs.

The main point of contention I would see is that "Defeat audio cache" was changed from Unknown/Yes/No to null/true/false. All of the others were strict booleans (could only be true or false).

Example:

import yaml# PyYAML, uses YAML 1.1
from ruamel.yaml import YAML # uses YAML 1.2

ruamel_yaml = YAML(saf=True)

with open('whipper_test.log') as open_file:
    log = open_file.read()

print(yaml.safe_load(log)['Ripping phase information']['Defeat audio cache']) # True
print(ruamel_yaml.load(log)['Ripping phase information']['Defeat audio cache']) # Yes

This follows from the discussion in #384 around this.

[MerlijnWajer]

We should make sure that this doesn't break existing logparsers.

[itismadness]

This will 100% break any logparsers that use a YAML 1.2 parser as it'll go from expecting (and operating on) strings for these fields to them now being booleans. However, how many logparsers exist out in the wild and given the pre-release status of whipper, is it not acceptable to have these kinds of quality-of-life breaks?

[Freso]

We should make sure that this doesn't break existing logparsers.

In some previous discussion (can’t remember if it was on GitHub or in the #whipper IRC channel), either you or @JoeLametta said that it’s fine to break log parsers until we hit the 1.0.0 (and I agree with that).

We should make sure to at least bump the minor version though for the next 0.x.x release if we do this, but we should already be bumping the minor for next release anyway (due to some other small log change, I think?).

Also, I think we should absolutely be using YAML 1.2 if possible.

[JoeLametta]

@itismadness Thanks for the pull request: LGTM. In order to merge it without CI failures, please add a Signed-off-by line in the commit's description as documented here.

[JoeLametta]

Merged in 0d69258.