fix: allow_to_create_new_org checks org autocreate [FC-0076]

[pomegranited]

Description

Updates the StudioHome API's allow_to_create_new_org to require both organization-creation permissions and settings.ORGANIZATIONS_AUTOCREATE to be enabled.

Previously, users with staff permission were allowed to attempt organization autocreation when creating a course or library using the Authoring MFE, but if ORGANIZATIONS_AUTOCREATE was disabled, they would get an error from the creation API.

ORGANIZATIONS_AUTOCREATE is enabled by default, but edx.org disables it.

Useful information to include:

• Which edX user roles will this change impact? Course Authors

Supporting information

Part of: openedx/frontend-app-authoring#1577

Testing instructions

See Authoring MFE PR.

Deadline

None

[openedx-webhooks]

Thanks for the pull request, @pomegranited!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[pomegranited]

For reference, the can_create_organizations value is set here:

edx-platform/cms/djangoapps/contentstore/views/course.py

Lines 1794 to 1798 in c5fabd5

	def user_can_create_organizations(user):
	"""
	Returns True if the user can create organizations.
	"""
	return user.is_staff or not settings.FEATURES.get('ENABLE_CREATOR_GROUP', False)

which is pretty different from the original allow_to_create_new_org. But it didn't make sense to me that we'd use a different default value for settings.FEATURES['ENABLE_CREATOR_GROUP'] AND require the user to be staff here.