bug: remove trpc-openapi as a sugested solution for exposing procedures as REST endpoints

[thomasreichmann]

Provide environment information

N/A

Describe the bug

In the trpc usage section of the docs, trpc-openapi is suggested as a community plugin to expose all trpc procedures as REST endpoints, but since the docs were created, the plugin has stopped being maintained and It doesn't seem like a consensus has been reached on which fork will succeed it.

create-t3-app/www/src/pages/en/usage/trpc.md

Lines 206 to 208 in fe85a23

	### Exposing every procedure as a REST endpoint
	If you want to expose every single procedure externally, checkout the community built plugin [trpc-openapi](https://github.com/jlalmes/trpc-openapi/tree/master). By providing some extra meta-data to your procedures, you can generate an OpenAPI compliant REST API from your tRPC router.

Reproduction repo

N/A

To reproduce

N/A

Additional information

I'd love to be able to use it in production, but since its maintainer is no longer supporting the project and has also not appointed someone to maintain it, nor specified which fork should act as the successor, maybe the t3 community could take the lead in maintaining a fork so that we could recommend it in the docs?