Alphabetically sort the list of portal types in the constraints configuration form [4.x]

[erral]

• I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
• I verified there aren't any other open pull requests for the same change.
• I followed the guidelines in Contributing to Plone.
• I successfully ran code quality checks on my changes locally.
• I successfully ran tests on my changes locally.
• If needed, I added new tests for my changes.
• If needed, I added documentation for my changes.
• I included a change log entry in my commits.

---

If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #320 for 4.x (Plone 6.1)

[mister-roboto]

@erral thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

[erral]

I guess that tests for 6.2 should be disabled in the 4.x branch, right?

[erral]

@jenkins-plone-org please run jobs

[erral]

@jenkins-plone-org please run jobs

[erral]

@mauritsvanrees @gforcada is it OK to have the 6.2 tests failing in this branch that is used for Plone 6.1?

[davisagli]

@erral This branch needs to be updated to not run the 6.2 tests.

[erral]

Ok, I created a new PR for that.

[erral]

@jenkins-plone-org please run jobs