Document definitions for ecosystem project types

Nobody has claimed this yet.

Given that we’ve repeatedly come across issues related to the fact that we don’t have exact definitions of what each type of ecosystem project is, let’s take the time to document what we’re referring to by each project type.

Here’s a list of the various types we’d need to define, in no particular order:
- Client (see: https://github.com/matrix-org/matrix.org/issues/3592)
- Server (see: https://github.com/matrix-org/matrix.org/issues/3595)
- Bridge (see: https://github.com/matrix-org/matrix.org/issues/3596)
- Integration (see: https://github.com/matrix-org/matrix.org/issues/3597)
- SDK (see: https://github.com/matrix-org/matrix.org/issues/3598)
- Distribution (see: https://github.com/matrix-org/matrix.org/issues/3599)
- Hosting Provider (see: https://github.com/matrix-org/matrix.org/issues/3594)
- Other (see: https://github.com/matrix-org/matrix.org/issues/3593)

Each project type was broken down into its own issue so we can address the issues without having to wait until all project types are defined.

Start by reading the linked issues for Client, Server, Bridge, Integration, SDK, Distribution, Hosting Provider, and Other to understand the separate definitions requested. Done means documenting an exact definition for each ecosystem project type, without waiting for all eight related issues to be completed.

Written by the indexing model from the issue text.