Add e2e tests on generated files.

[cube2222]

This issue is two-fold.

The main point is that we should, after generating static registry files, spin up a local http server to mock the registry, and run some e2e tofu executions with it, to make sure it's working well.

This should be executed on generated files prior to syncing them to the prod bucket, and ideally also on each pull request.

[kislerdm]

@cube2222 Hey Kuba, I'd be happy to give a hand with the issue this week.

[cube2222]

Apologies for the late response, are you still interested in taking this @kislerdm?

Also, just to clarify the issue a bit more, the end to end tests should be very limited. One or two executions using some modules like local file. The goal is for this to not slow down the sync workflow too much.

The http server would ideally also be something simple off-the-shelf, like nginx serving on localhost. But if it’s not easy to do, it could also be a simple go binary.

[virtualroot]

Do these jobs need to be fixed? Both workflows have zero runs:

• https://github.com/opentofu/registry/actions/workflows/validate-json-module.yml
• https://github.com/opentofu/registry/actions/workflows/validate-json-provider.yml