fix: Fix documentation for mongodbatlas_api_key (#1363)

Author: andreaangiolillo

website/docs/r/api_key.html.markdown

@@ -35,22 +35,6 @@ The following are valid roles:
   * `ORG_READ_ONLY`
   * `ORG_MEMBER`
 
-~> **NOTE:** Project created by API Keys must belong to an existing organization.
-
-### Programmatic API Keys
-api_keys allows one to assign an existing organization programmatic API key to a Project. The api_keys attribute is optional.
-
-* `api_key_id` - (Required) The unique identifier of the Programmatic API key you want to associate with the Project.  The Programmatic API key and Project must share the same parent organization.  Note: this is not the `publicKey` of the Programmatic API key but the `id` of the key. See [Programmatic API Keys](https://docs.atlas.mongodb.com/reference/api/apiKeys/) for more.
-
-* `role_names` - (Required) List of Project roles that the Programmatic API key needs to have. Ensure you provide: at least one role and ensure all roles are valid for the Project.  You must specify an array even if you are only associating a single role with the Programmatic API key.
- The following are valid roles:
-  * `GROUP_OWNER`
-  * `GROUP_READ_ONLY`
-  * `GROUP_DATA_ACCESS_ADMIN`
-  * `GROUP_DATA_ACCESS_READ_WRITE`
-  * `GROUP_DATA_ACCESS_READ_ONLY`
-  * `GROUP_CLUSTER_MANAGER`
- 
  ## Attributes Reference
 
 In addition to all arguments above, the following attributes are exported: