Ideas for `version` command

[remcotolsma]

• [x] Before running check if working tree is clean (git status or git status --short)
• [ ] Before release type choice show git log information.
• [x] Display auto generated changelog first, and let user choose to open editor.
• [ ] Add support for PR's in auto genereated changelog (gh pr list).
• [ ] Add support for issues in auto genereated changelog (gh issue list).
• [x] Auto create tag like npm version
• [x] Auto create draf GitHub release gh release create <tag> --draft --generate-notes
• [x] Check for new added Composer requirements.
• [x] Check for removed Composer requirements.
• [x] Add option to include changelog of Composer updates.
  • Read vendor/pronamic/repository/CHANGELOG.md version entry.
• [x] Warn about dev- requirements in composer.json?
• [x] Check composer outdated or composer outdated --direct for outdated packages?
• [x] Rename vendor/bin/wp-deployer to vendor/bin/pronamic-deployer for branding?

[remcotolsma]

Changelog parse sections: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements

[remcotolsma]

Auto create tag like npm version

• https://github.com/npm/cli/tree/7018b3d46e10ea4d9d81a478dbdf114b6505ed36/workspaces/libnpmversion
• https://github.com/npm/cli/blob/7018b3d46e10ea4d9d81a478dbdf114b6505ed36/workspaces/libnpmversion/lib/version.js.

[remcotolsma]

Added "Check composer outdated or composer outdated --direct for outdated packages?" to the tasks.

[remcotolsma]

Added "Rename vendor/bin/wp-deployer to vendor/bin/pronamic-deployer for branding?" to the tasks.