`tmt run --recipe` uses the latest test script file, but it does not update the plan based on test metadata

[tcornell-bus]

Reproducer:
To get a test to pass, I realized I needed to add a package using the require key in the test metadata. I updated the main.fmf test metadata file, and then I re-executed the test using a past recipe.yaml with that test specified in it. The subsequent plan execution did not include the just-added package in the prepare requires step. But it did include an update to the runtest.sh test script.

Seems like tmt run --recipe recipe.yaml should also re-evaluate test metadata.

---

Reproducer:

$ tmt init --template base
$ tmt run

It should fail because the tests/example/main.fmf is missing require: tmt
Add the require to the main.fmf file.
Add echo "testing" to the test.sh

tmt run --recipe /var/tmp/tmt/run-xxx/recipe.yaml

The package will not be installed in the requires prepare step, and the test will still fail, but the added echo will be present.

[therazix]

From the triage meeting: This behavior is expected. tmt needs to generate a new recipe using the new test metadata. It would be nice to mention this in documentation.