Release version 1.6.0

[jeffpaul]

This issue is for tracking changes for the 1.6.0 release. Target release date: Friday, October 23rd.

Pre-release steps

• Complete review of PR Azure Image OCR #228, resolve issues, and merge
• Complete review of PR feat: add crop command #236, resolve issues, and merge
• Complete review of PR Update/docs #239, resolve issues, and merge

Release steps

• Branch: Starting from develop, cut a release branch named release/1.6.0 for your changes.
• Version bump: Bump the version number in classifai.php, classifai.pot, config.php, package-lock.json, package.json, and readme.txt if it does not already reflect the version being released.
• Changelog: Add/update the changelog in CHANGELOG.md.
• Translations: Update the .pot file by running npm run makepot.
• Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .github/action-release/rsync-filter.txt.
• Readme updates: Make any other readme changes as necessary in README.md and readme.txt.
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into trunk (git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
• Check the build: Check out the trunk branch and test for functionality locally.
• Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases and in the WordPress admin as an update as well.
• Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
• Punt incomplete items: If any open issues or PRs which were milestoned for 1.6.0 do not make it into the release, update their milestone to 1.7.0 or Future Release.