Release 1.33.0

[bajertom]

Follow the steps below to create a new major or minor release:

• Use git log --oneline --no-decorate x.y-1.. to generate the changelog
• Update overview.rst with new contributors since the last release
• Review the release notes in releases.rst, update as needed
• Add a Release tmt-x.y.0 commit with the specfile update
• Create a pull request with the commit, ensure tests pass, merge it

Release a new package to Fedora and EPEL repositories:

• Move the fedora branch to point to the new release
• Tag the commit with x.y.0, push tags git push --tags
• Create a new github release based on the tag above
• Check Fedora pull requests, make sure tests pass and merge

Finally, if everything went well:

• Close the corresponding release milestone
• Once the non development copr build is completed, move the quay branch to point to the release commit as well to build fresh container images.

Handle manually what did not went well:

If the automation triggered by publishing the new github release was not successful, publish the fresh code to the [pypi](https://pypi.org/project/tmt/) repository manually using make wheel && make upload

If there was a problem with creating Fedora pull requests, you can trigger them manually using /packit propose-downstream in any open issue.

[bajertom]

/packit test --identifier full

[bajertom]

/packit build

[psss]

/packit build

[psss]

@bajertom, everything's green! I guess we're ready to release :)