Add {input,output}_visualizer_args and example visualizers

[mpsijm]

Closes #351 and closes #459.

I've tested the example visualizers in the "maximal" problem with https://github.com/RagnarGrootKoerkamp/BAPCtools/tree/draft, with the following side-notes:

• The visualizer in BAPCtools currently only generates images under data/ with a proper generators/generators.yaml, so I temporarily wrote one:

  Temporary generators/generators.yaml:

  solution: /submissions/accepted/accepted.py
  version: 2025-04
  
  data:
    sample:
      testdata.yaml:
        test_case_visualizer_args: [sample]
        output_visualizer_args: [sample]
      data:
        "1":
          in: "41"
  
    secret:
      testdata.yaml:
        test_case_visualizer_args: [secret]
        output_visualizer_args: [secret]
      data:
        "1":
          in: "13"
        "2":
          in: "-100"
        "3":
          in: "99"
        "4":
          in: "0"

• BAPCtools does not support the include/ (yet?), so it should be invoked as bt generate --no-solution --no-validators

• BAPCtools still uses testdata.yaml, I renamed this manually to test_group.yaml after running bt generate

  • Edit: BAPCtools uses test_group.yaml as well now! 🎉

Nonetheless, the "maximal" problem should be spec-compliant (and at some point in the future, BAPCtools should run it without issues as well) 😄

[niemela]

How can test_case_visualizer_args be used if "invocation instructions" are needed?

It would be great if we could specify invocation, as we do with output visualizers.

[niemela]

Isn't an input visualizer also a "visualizer program"?

Suggested change

	A visualizer program must be an application (executable or interpreted) capable of being invoked with a command line call. It is invoked using the same arguments as the output validator, except that `output_validator_args` is replaced with `output_visualizer_args`.
	An output visualizer program must be an application (executable or interpreted) capable of being invoked with a command line call. It is invoked using the same arguments as the output validator, except that `output_validator_args` is replaced with `output_visualizer_args`.

[mpsijm]

Yep, and I found some more inconsistencies when looking at the related phrases, thanks! 😄

[niemela]

@mpsijm Could you rebase?

[mpsijm]

Done! 😄