Implementations catalog upgrade: explain usage

[ElPaisano]

Addresses #1673

[lidel]

This gives false impression that "Lassie API" is something special. It is not.
We should not confuse the reader by mentioning it, the only thing that docs should mention is Gateway interface defined by https://specs.ipfs.tech/http-gateways/, and legacy Kubo RPC:

Suggested change

	If you'd like to use IPFS over standard HTTP, you have several options:
	- If you simply want to retrieve data, use the [Lassie client HTTP API](https://github.com/filecoin-project/lassie/#http-api).
	- You can control an IPFS Kubo node using HTTP via the [Kubo RPC API](../reference/kubo/rpc.md), with the same range of functionality available via the [Kubo CLI](kubo/cli.md). There are multiple [RPC API clients in multiple languages](../reference/kubo-rpc-cli.md) to choose from.
	- For an implementation and runtime agnostic HTTP interface, use an [IPFS gateway](../reference/http/gateway.md).
	If you'd like to use IPFS over standard HTTP, you have several options:
	- If you simply want to retrieve data, use the generic [IPFS gateway](../reference/http/gateway.md)
	- You can control an IPFS Kubo node using HTTP via the [Kubo RPC API](../reference/kubo/rpc.md), with the same range of functionality available via the [Kubo CLI](kubo/cli.md). There are multiple [RPC API clients in multiple languages](../reference/kubo-rpc-cli.md) to choose from.

[lidel]

ipfs-lite is written in Go, not Rust :)

Suggested change

	- For embedded applications in Rust, use [ipfs-lite](https://github.com/hsanjuan/ipfs-lite).
	- For lightweight embedded applications in GO, use [ipfs-lite](https://github.com/hsanjuan/ipfs-lite).

[lidel]

Suggested change

	| ipfs cluster | <https://github.com/ipfs/ipfs-cluster> | go | Orchestration for multiple Kubo nodes via CRDT / Raft consensus |
	| ipfs cluster | <https://ipfscluster.io> | go | Orchestration for multiple Kubo nodes via CRDT / Raft consensus |

[lidel]

Cluster has a very nice website:

Suggested change

	For complex applications that require data orchestration across a swarm of IPFS daemons, use [ipfs-cluster](https://github.com/ipfs-cluster/ipfs-cluster), which allocates, replicates and tracks a global pinset distributed among multiple peers.
	For complex applications that require data orchestration across a swarm of IPFS daemons, use [ipfs-cluster](https://ipfscluster.io), which allocates, replicates and tracks a global pinset distributed among multiple peers.

[lidel]

Suggested change

The purpose of this page is to catalog the many IPFS <VueCustomTooltip label="Software, written in any programming language, with functionality to process and transmit content-addressed data. Some implementations are optimized for specific use cases or devices, or use different subsystems to handle content-addressed data. There are multiple specififactions in IPFS for handling content-addressed data, and not all implementations implement them." underlined multiline is-medium>implementations</VueCustomTooltip> and tools, as well as provide general guidance on choosing and implementation or tool to work with.

The purpose of this page is to catalog the many IPFS <VueCustomTooltip label="Software, written in any programming language, with functionality to process and transmit content-addressed data. Some implementations are optimized for specific use cases or devices, or use different subsystems to handle content-addressed data. There are multiple specifications in IPFS for handling content-addressed data, and not all implementations implement them." underlined multiline is-medium>implementations</VueCustomTooltip> and tools, as well as provide general guidance on choosing and implementation or tool to work with.

[lidel]

I think we want to point people at boxo, then kubo, then the rest.
(Lassie is limited to "leach" mode, it should not be suggested as the first option)

Suggested change

	- To quickly retrieve data with minimal complexity and overhead, use the [Lassie client Golang library](https://github.com/filecoin-project/lassie/#golang-library) in your applications.
	- For more complicated applications requiring the full range of IPFS functionality, use Kubo or Boxo.
	- To create custom IPFS node tailored to your individual needs, try [Boxo SDK](https://github.com/ipfs/boxo).
	- For applications requiring the full range of IPFS functionality, such as providing data to other peers, use [Kubo](https://github.com/ipfs/kubo).
	- To quickly retrieve data with minimal complexity and overhead, use the [Lassie client Golang library](https://github.com/filecoin-project/lassie/#golang-library) in your applications.