Move (most of) /docs/orga/ under /community

[jaimergp]

PR Checklist:

• note any issues closed by this PR with closing keywords

  • Closes Move org files from sphinx to community/orgs #2066
  • Closes Move meeting minutes to community/meeting-minutes #2068

• if you are adding a new page under docs/, you have added it to the sidebar in docs/sidebar.json

• put any other relevant information below

• Part of Redesigning conda-forge.org #1971

• Moves the "Organisation documentation" over to a new section under /community. This helps keeping things tidy in terms of scope, and should also provide better search results once Algolia learns the new structure.

• I didn't move the "orga/guidelines" page and instead put it under "docs/maintainer", where it fits better.

• I added a brief Code of Conduct page with the same contents as we have in the README for now.

• I added a small index page for the meeting minutes, with the same info about the meetings we already had in the README.

[netlify]

✅ Deploy Preview for conda-forge-previews ready!

Name	Link
🔨 Latest commit	bbce3f0
🔍 Latest deploy log	https://app.netlify.com/sites/conda-forge-previews/deploys/65dfcd527b813b0008e13f95
😎 Deploy Preview	https://deploy-preview-2093--conda-forge-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jakirkham]

Could we cleanup the commit history a bit and exclude the pure file moves from git blame?

ref: https://github.blog/changelog/2022-03-24-ignore-commits-in-the-blame-view-beta/

[jaimergp]

We're squashing all these big PRs so I'm not sure how much that'd help. The idea is that if someone is looking into the git history, they'll find the squashed merge, but they can check the PR for individual bits.

Edit: I see some PRs have been merged with a regular merge commit. I'll add the ignore rev file once we are done with the overhaul.