[Feature] Update environment controller and remove ability to update environments from putOrganization

[mknowlton89]

Description of Feature

As part of an on-going effort to reduce to capabilities of organizations.controller, we should not allow an org to update an org's environments via the organization.controller's putOrganization method.

We should block that functionality and instead add it explicitly to the environment.controller. Currently, we're missing a putEnvironment method (currently only supports updating multiple environments).

It is also missing a deleteEnvironment method.

When we do this work, we should also split out the PermissionsClass.canCreateOrUpdateEnvironment method into separate canCreate and canUpdate methods, with the canUpdate method taking the shape of other canUpdate methods where we take in the existing environment, check to make sure the user has permission to update it, as well as the updates and make sure that after the updates, the user still have permission to edit.

Sample code for the canUpdate method (has not been tested, so just use as a starting point)

  public canUpdateEnvironment = (
    existing: Pick<Environment, "projects" | "id">,
    updates: Pick<Environment, "projects" | "id">
  ): boolean => {
    const existingProjects = existing.projects?.length
      ? existing.projects
      : [""];
    if (
      !existingProjects.every((project) =>
        this.hasPermission("manageEnvironments", project, [existing.id])
      )
    ) {
      return false;
    }

    if ("projects" in updates) {
      const updatedProjects = updates.projects?.length
        ? updates.projects
        : [""];

      if (
        !updatedProjects.every((project) => {
          this.hasPermission("manageEnvironments", project, [updates.id]);
        })
      ) {
        return false;
      }
    }
    return true;
  };

Related Issues

• PR where we introduces canCreateOrUpdateEnvironment - Migrates manageEnvironments to permission Class. #2484