7.4.0 Release

Release blockers
----------------
- None

Pre-release
---
- [x] Verify that no other open issue needs to be addressed before the release.
- [x] Test against other ETS packages and other ETS-using projects
- [x] Check MANIFEST, requirements, changelog are still up to date.
- [x] Test building the documentation

Release
-------
- [x] Create branch `release/` from `main` branch.
- [x] Set release to ``, and set `IS_RELEASED` is true; commit
- [x] Install from source distribution and run tests again
- [x] Open a PR against `main` with this being the last commit so that CI is built on the release commit
- [x] Once CI is done building merge PR
- [x] Bump the minor version number i.e. `` and set `IS_RELEASED` to false; commit.
- [x] Open and then merge a separate PR against `main`
- [x] Create a branch `maint/` from the release commit.
- [x] bump the micro version number i.e. `` and set `IS_RELEASED` to false; commit.
- [x] push the new branch to github
- [x] From the commit at which `IS_RELEASED` is true and version is ``, tag (annotated!) `git tag -a -m "Release " `
- [x] Push the tag `git push origin `
- [x] Make PR targeting `gh-pages` branch: Generate documentation and copy the content to the branch. Verify that the resulting index.html looks good.
- [x] Upload to PyPI
- [x] Test the PyPI package

Post-release
-------------
- [ ] Package update for `enthought/free` repository (for EDM)
- [x] Backport release note and change log to ``main``, and possibly `maint/` branch.
- [x] Update GitHub Release pages https://github.com/enthought/traitsui/releases
- [ ] Announcement (e.g. Google Group)