Feature/11777 min requirements (#13662)

* i added a .editorconfig file that enforces on save what the git commit hook tests require. This should reduce the headache by supplying automatic compliance to anyone having that feature enabled in their IDE

* added ignore for devbox and aider. both are dev tools that some may use for working on the project that create unwanted artifacts

* housekeeping on the .gitignore file

* updated the SCIM and SAML guides to speak to the cardinality of applications to pulumi organizations that can be created with each type of sso protocol

* added devbox config to make it easier for devbox users to contribute to the project

* updated the SCIM and SAML guides to speak to the cardinality of applications to pulumi organizations that can be created with each type of sso protocol

* assets changed

* added tooling config files to the prettierignore so that they don't effect the pre commit hook checks

* updated message on note to be more clear per code review and updated style to be more consistent

* per review I reduced the redundancy of the message from being in just the landing page for SAML and SCIM

* per review I reduced the redundancy of the message from being in just the landing page for SAML and SCIM

* added comments linking to the benchmarking repo

* remove uncessary files and modifications from branch

* fix environment variable name typo

---------

Co-authored-by: Troy Howard <[email protected]>

content/docs/iac/download-install/_index.md

@@ -591,6 +591,31 @@ To install, run our installation script:
 
 {{% /chooser %}}
 
+## Minimum system requirements
+
+<!--
+## Rationale for Minimum System Requirements
+
+Please see https://github.com/pulumi/pulumi-benchmarking where we have a benchmarking codebase to represent typical pulumi actions.
+
+The results from this benchmark were 10% CPU utilization on a Apple M1 Pro for the apply and 20% CPU utilization for the destroy.
+The memory usage for both was 1.5GB.
+
+So the following recommendations were made to add some headroom for the typical pulumi actions, espciailly for larger projects.
+-->
+
+The following are general recommendations for minimum system requirements when using Pulumi. Actual performance may vary based on the SDK runtime, providers used, operating system and the size and complexity of your infrastructure deployments. However, the following requirements should be considered a minimum to account for typical usage.
+
+| Component      | Recommendation                                                                                                              |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------|
+| **CPU**        | 2 GHz or faster processor (or equivalent vCPUs for cloud environments)                                                      |
+| **RAM**        | 4 GB or more                                                                                                                |
+| **Disk Space** | 1 GB or more free disk space (additional space may be required when using multiple runtimes, providers, or large codebases) |
+
+{{% notes "info" %}}
+System requirements can vary significantly depending on the providers used and how packages/plugins are managed. Using multiple providers or large plugins may require additional disk space. Performance may also be impacted by the runtime for the SDK you are using (e.g., Node.js, Python, Go), the operating system, and how packages are managed in your development environment. Additionally, CPU and RAM requirements can be influenced by the complexity of your infrastructure, the runtimes, and the packages/plugins used, as well as the ability to take advantage of parallel processing during `pulumi plan` and `pulumi apply` operations.
+{{% /notes %}}
+
 ## Uninstalling Pulumi
 
 To uninstall Pulumi, use your installation method's command of choice. If you installed Pulumi manually, delete the `pulumi` directory that you created. Afterwards, remove the `.pulumi` folder from your home directory which contains plugins and other cached metadata.