Cloning a deployment environment with dedicated agents leads to Access Denied errors

Issue Summary

Non-admin users get Access Denied errors when trying to clone a deployment environment with dedicated agents.

Steps to Reproduce

What permissions are needed?

Regular users (i.e. users without administrative access) can clone deployment environments in Bamboo provided they have the following permissions:

1. Access permission under the Bamboo admin > Overview > Security > Global permissions page.
2. View and Edit permissions on the deployment project.
3. View permission on the deployment environment they're trying to clone.

As a Bamboo admin

1. Create an environment inside one of your deployment projects.
2. Dedicate an agent to build that environment.
3. Create a new user (e.g. test-user).
4. Make sure the user has the permissions mentioned above and is NOT an admin or restricted admin.

As a regular user

1. Log in to Bamboo with the user account created in the previous step.
2. Edit the deployment project.
3. Clone the deployment environment created in the previous step.

Expected Results

I can think of a few scenarios that differ from the results we have today.

1. Let users clone the environment and remove the agent dedication in the cloned environment.
2. Display a more meaningful error message to let users know why they cannot clone the environment i.e. because there are dedicated agents they don't have access to manage.
3. Do not display the 'Clone' option to the user in the first place.

Actual Results

Users get the following Access Denied error and do not understand why they're unable to clone the environment.

Workaround

1. Ask an admin or restricted admin to remove the agent dedication and try to clone the environment again.
2. Ask an admin to clone the environment for you and remove the agent dedication in the cloned environment.
3. Dedicate the agent to build the deployment project instead of the deployment environment. This will allow regular users to clone the deployment environment.