Release 1.64.0 (#4436)

### Notes, contributors, tests

- [x] Review the release notes content and update the text as needed
- [x] Write release notes for any essential changes which were missed
- [x] Verify the rendering locally using `make docs` or the
`docs/readthedocs.org:tmt` GitHub action check
- [x] Use `./scripts/list-new-contributors` to identify new
contributors, update `docs/overview.rst` accordingly
- [x] Commit and push all release notes and contributor changes
- [x] Make sure that the full test coverage has been successfully
executed
- [x] Merge the release pull request

### Tag, release, downstream

- [ ] Make sure you have the release commit: `git checkout main && git
pull`
- [ ] Tag the commit with `x.y.z`, push tags using `git push --tags`
- [ ] Create a new [github
release](https://github.com/teemtee/tmt/releases/) based on the tag
above
- [ ] Mention the most important changes in the release name, do not
include version
- [ ] Push the “Generate release notes” button to create the content,
publish the release
- [ ] Check Fedora [pull
requests](https://src.fedoraproject.org/rpms/tmt/pull-requests) and
review proposed changes
- [ ] Make sure that tests pass and merge individual pull requests

### Milestones, container images

- [ ] Use the bulk edit in the [milestone
view](https://github.com/orgs/teemtee/projects/1/views/19) to set the
milestone for all issues and pull requests included in the sprint
- [ ] Close the corresponding [release
milestone](https://github.com/teemtee/tmt/milestones)
- [ ] Once the non development [copr
build](https://copr.fedorainfracloud.org/coprs/g/teemtee/stable/builds/)
is completed, run the
[publish-images](https://github.com/teemtee/tmt/actions/workflows/publish-images.yml)
workflow to build fresh container image.

---------

Signed-off-by: Cristian Le <git@lecris.dev>

Author: LecrisUT

docs/releases/1.64.0/4307.fmf

@@ -0,0 +1,4 @@
+description: |
+  The :ref:`prepare shell</plugins/prepare/shell>` and
+  :ref:`finish shell</plugins/finish/shell>` plugins now produce results in the
+  ``results.yaml`` file of the step.

docs/releases/1.64.0/4320.fmf

@@ -0,0 +1,2 @@
+description: |
+  The guest data is now saved in the ``results.yaml`` for each phase execution.