API V3: Don't allow leaking teams through expandable fields

[stsewd]

• teams is removed from organizations and projects
• A new endpoint was added to list teams from an organization
• I didn't implement something like that for projects, do we have the need for something like that?
• We used to have two serializes for the organizations, one without expandable fields, and the other with expandable fields (only teams). There is no need for this anymore, so they were merged.
• Tests are on .com

Ref https://github.com/readthedocs/readthedocs-corporate/issues/1736

---

📚 Documentation previews 📚

• User's documentation (docs): https://docs--11471.org.readthedocs.build/en/11471/

• Developer's documentation (dev): https://dev--11471.org.readthedocs.build/en/11471/

[stsewd]

This was allowing /organizations/projects/{project} which we don't want, since all project endpoints are under /projects/{project}.

[stsewd]

If the owner didn't belong to any admin teams, we were not granting permissions :_

[agjohnson]

Just chiming in here on the frontend/docs pieces, these look good. I'm leaving review on the API changes for @humitos, he has most context on the API.

[ericholscher]

This seems reasonable to me 👍

Does it need any updates from the permissions changes (#11485)