Create Environment permission does not allow user to create environment

[matthewelwell]

Describe the bug

Users with Create Environment permission should be able to create a new environment. Since the create environment workflow uses the clone endpoint if there are existing environments, this is not working.

To Reproduce

Steps to reproduce the behaviour:

1. Give a user View Project and Create Environment permissions on a project, and view environment permissions on at least one other environment
2. Login as the user with these permissions and attempt to create a new environment
3. Notice that the request to create the new environment (by cloning another one) fails with 403 and the environment is not created

Expected behavior

The environment is created successfully.

Screenshots

How are you running Flagsmith?

• Self Hosted with Docker
• Self Hosted with Kubernetes
• SaaS at flagsmith.com
• Some other way

Tested via SaaS but affects all deployment types.

Additional context

N/a

[matthewelwell]

I suggest that we change the permissions on the clone environment endpoint to use the CREATE_ENVIRONMENT permission.

Currently the endpoint requires the user to be an admin of the environment they are trying to clone but I think this is not necessarily by design. An alternative solution would be for the FE to only show environments for which they are admins for the user to clone from, but I don't think this is the desired outcome.