Audit of the current infrastructure, tooling, and credentials

[jaimergp]

📌 Summary

The goal is to audit and document existing conda-forge's infrastructure.

This will be done in public. We need to ensure no critical security details such as credentials are exposed.

📝 Background

To propose technical debt reduction measures and ensure the long-term viability of the project and its growing ecosystem, we first need to understand and document the current status of the platform.

Expected challenges:

• Large number of moving parts across services and platforms
• Several accounts and credentials key to the normal operating conditions
• Lack of documentation for each part
• Scattered institutional knowledge

### 🚀 Tasks / Deliverables
- [x] #27
- [x] RST to MD in Docusaurus, permanently, with git history preservation if possible: https://github.com/conda-forge/conda-forge.github.io/pull/2084
- [ ] #31
- [ ] https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/55
- [ ] #37
- [ ] https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/42
- [ ] https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/3
- [ ] https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/56

📅 Estimated completion

This task should be finished in the first six months.

ℹ️ References

• conda-forge's Security and Systems Sub-Team
• conda-forge's Bot Sub-Team
• conda-forge repositories that are not regular feedstocks
• regro/cf-scripts documentation
• Talks about conda-forge (some cover infrastructure)
• regro.github.io