Re-work config file

Add an explicit section for tests that would be a dictionary so that an example config would look like:

```
tests:
test_h265_color:
app: ffmpeg
comparisontest:
- testtype: idiff
- testtype: assertresults
tests:
- assert: less
value: max_error
less: 0.00195
description: h265 color tests of different pix-fmts
encoding_template: ffmpeg -y {input_args} -i "{source}" {encoding_args}
-y "{outfile}"
name: test_h265_color
sources:
- ../sourceimages/chip-chart-1080-noicc.png.yml
- ../sourceimages/chip-chart-1080-16bit-noicc.png.yml
- ../sourceimages/smptehdbars_16.png.yml
suffix: .mp4
wedges:
yuv444p10lex265: &basex265
-c:v: libx265
-vf: '"scale=in_color_matrix=bt709:out_color_matrix=bt709"'
-color_primaries: bt709
-color_range: tv
-color_trc: bt709
-colorspace: bt709
-pix_fmt: yuv444p10le
-preset: placebo
-x265-params: lossless=1
-tag:v: hvc1
-profile:v: main444-10

yuv444p12lefullx265:
<< : *basex265
-vf: '"scale=in_range=full:in_color_matrix=bt709:out_range=full:out_color_matrix=bt709"'
-color_range: pc

videotoolbox_h265_bgra:
<< : *basex265
-c:v: hevc_videotoolbox
#-vf: '"scale=in_range=full:in_color_matrix=bt709:out_range=full:out_color_matrix=bt709"'
-color_range: pc
-colorspace: rgb
-profile:v: main
-pix_fmt: bgra

test_h265_color_420:
app: ffmpeg
comparisontest:
- testtype: idiff
compare_image: ../sourceimages/chip-chart-1080-16bit-noicc-yuv420p10le.png
- testtype: assertresults
tests:
- assert: less
value: max_error
less: 0.00195
description: h265 color tests of different pix-fmts
encoding_template: ffmpeg -y {input_args} -i "{source}" {encoding_args}
-y "{outfile}"
name: test_h265_color
sources:
- ../sourceimages/chip-chart-1080-16bit-noicc.png.yml
suffix: .mp4
wedges:
yuv420p10le: &basex265
-c:v: libx265
-vf: '"scale=in_color_matrix=bt709:out_color_matrix=bt709"'
-color_primaries: bt709
-color_range: tv
-color_trc: bt709
-colorspace: bt709
-pix_fmt: yuv420p10le
-preset: placebo
-x265-params: lossless=1
-tag:v: hvc1
-profile:v: main444-10

reports:
description: This is testing h265 color encoding.
directory: hevc-color-encode
name: hevc-color-tests
templatefile: colorweb.html.jinja
title: Ffmpeg encoding guide tests

```

I might also remove some of the duplicate info, such as the name, and in the reports, the directory and name fields.

Utilisez la configuration d’exemple de l’issue comme structure cible. Examinez les sections tests et reports proposées, puis déterminez quels champs en double, notamment name, directory et report name, doivent être conservés. Le travail est terminé lorsque la structure de configuration est cohérente et que l’exemple reflète fidèlement le format pris en charge.

Rédigé par le modèle d'indexation à partir du texte de l'issue.