Create a script to translate problem packages from legacy version

[niemela]

See also RagnarGrootKoerkamp/BAPCtools#295

[niemela]

The translator should:

1. Determine if it is possible to translate. The main reasons for why it wouldn't be is if a grader was used or a validator is written in a language son supported in the new version.
2. If it is not possible, explain why.
3. If it is possible, do it. :).

I think it should/could assume that a given package is "correct". I.e. package validation is a separate tool.

It might also be somewhat useful to support translation between every pair of versions, but translating from the new to the old would of course have many more potential to not be possible.

[niemela]

@sjoqvist

[mpsijm]

Also linking Kattis/problemtools#285 and RagnarGrootKoerkamp/BAPCtools#432 here 😄

[niemela]

@mpsijm regarding your comment over at Kattis/problemtools#285. Is there a list somewhere of what extensions BAPCtools has on top of the spec?

[mpsijm]

This list is not documented, but from the top of my head:

• problem.yaml: keys verified, comment, limits.generator_time, limits.visualizer_time
• answer_validators/
• generators/generator.yaml, which includes:
  • Generating test case inputs based on configured generator programs
  • Generating test case answers based on one jury submission marked as "solution"
  • Visualizer (this would be equivalent to the input_visualizer/ in 2023-07-draft, but this already existed in legacy)
  • .desc and .hint files
• Contest metadata in contest.yaml and problems.yaml (but that's probably outside the scope of this problem package format specification)

[niemela]

@mpsijm Could you elaborate on that list?

Are there any more things?