Smoke testing

[ms14981]

Things to note:

• The package versions for the generators are not correct in the logs: Version numbers are not updated in package jsons #191
• The generator-options command targets the JS generator, and assumes a --moduleFormat option. If this ever changes, the smoke test will fail.
• The test-generators command targets the TS generators and assumes that all scenarios should be passing. This may not be true, e.g. in the development of a new feature file. Can this be shown as a warning, instead of a failure?
• The forge command assumes the C# generator can successfully run the forge command on the PetStore. It also assumes that the PetStore API server is up when the command is run. We could change to using a local test schema.
• The smoke test could be expanded to test all generators on all commands. Maybe one smoke test for each generator (three commands per generator).
• This smoke test has highlighted that the relative paths work differently in the generator-options command and the test-generators command, which is confusing: JS vs TS: Relative paths are treated differently in different commands #195

Success case (e.g. https://github.com/ScottLogic/openapi-forge/actions/runs/4552435246/jobs/8027766468):

Failure case (e.g. https://github.com/ScottLogic/openapi-forge/actions/runs/4552118020/jobs/8027052646):

[ms14981]

Closing in favour of #194