Test ethdebug program output against corresponding schema

[clonker]

• clones the ethdebug format repository into a tempdir
• uses that to build a schema repository so that individual fragments of the schema can be used to construct a validator, e.g.,

  validator = jsonschema.Draft202012Validator(
      schema={"$ref": "schema:ethdebug/format/program"},
      registry=ethdebug_schema_repository
  )

• has a parametrized test that tests (currently) all combinations of requested output in
  • ["evm.bytecode.ethdebug", "evm.deployedBytecode.ethdebug"] and
  • test files ["input_file.json", "input_file_eof.json"]

Due to the EOF test and invalid instructions with negative offsets, this PR depends on #15994 which fixes/implements these things.

The output without these fixes looks like this: https://app.circleci.com/pipelines/github/ethereum/solidity/39379/workflows/982d78f3-9c42-4849-b48f-cd01a82cd4a4/jobs/1822516

[aarlt]

I think it would be nice to have this already implemented in a way that it will dynamically pick files and test it.. e.g. the test will search for all json files defined in a specific directory and will then verify whether ethdebug output is correct

[clonker]

this is already possible by adding more stuff to the params kwarg. depending on what you want to test, you can rglob json files from some directory ahead of test time and add them there to the list

[aarlt]

I think it would be awesome to integrate this within our command-line tests. I could imagine that it would be really nice to allow the following: if in a command-line test directory the special file verify-ethdebugis present, the produced schema will be verified, similar to that special file strip-ethdebug to remove the ethdebug data from the output. It would be great if verify-ethdebug and strip-ethdebug could be present at the same time within a single test directory, this might allow the verification of the ethdebug data before the actual removal is done.

[github-actions]

This pull request is stale because it has been open for 14 days with no activity.
It will be closed in 7 days unless the stale label is removed.

The base branch was changed.

[matheusaaguiar]

This was already approved before, so I just gave it a quick pass and approved again.