🧹 refactor: change the way we control project and env permissions

[cosmos-explorer]

The following changes:

• Rename ListProjects to CanAccessProject: can be applied to both general and specific projects
  - if applied to general projects: can access to all projects
  - if applied to a specific project: can access to a specific project
  Projects without CanAccessProject action granted won't be displayed in the UI

• Remove ListEnvironments: if a user can access a project, he can access to all its envs
  except the envs whose CanAccessEnv permission is explicitly denied

• Rename AccessEnvs to CanAccessEnv

This PR brings a breaking change, need to update the MongoDb with the following scripts:

• Rename the action ListProjects to CanAccessProject

db.Policies.updateMany(
  {
    "statements.actions": "ListProjects"
  },
  {
    $set: {
      "statements.$[elem].actions.$[action]": "CanAccessProject"
    }
  },
  {
    arrayFilters: [
      {
        "elem.actions": "ListProjects"
      },
      {
        "action": "ListProjects"
      }
    ]
  }
);

• Rename the action AccessEnvs to CanAccessEnv

db.Policies.updateMany(
  {
    "statements.actions": "AccessEnvs"
  },
  {
    $set: {
      "statements.$[elem].actions.$[action]": "CanAccessEnv"
    }
  },
  {
    arrayFilters: [
      {
        "elem.actions": "AccessEnvs"
      },
      {
        "action": "AccessEnvs"
      }
    ]
  }
);

• Remove the action ListEnvs

db.Policies.updateMany(
  {},
  {
    $pull: {
      "statements.$[].actions": "ListEnvs"
    }
  }
);

[deleteLater]

LGTM