Improve messaging around non-js use

[LorisSigrist]

The Inlang CLI is distributed via npm. This is incredibly convenient if you are working in JS land, but frustrating for everyone else.

For example, if you are using PHP, you likely don't have node lying around to run npx @inlang/cli. But PHP developers could still greatly benefit from the integration with the Inlang ecosystem. While they don't need an equivalent to Paraglide or i18next, thanks to the excellent i18n support from PHP frameworks, they would still benefit from Lint Rules, Fink and Parrot. Given that basically every PHP i18n library just reads from JSON files we already support that, they just need to install the CLI.

It's not very clear in our messaging that Inlang works in non-js projects aswell. I propose that we expand our messaging, write guides and make it easier to install and use the CLI in non-js projects. If the Inlang CLI were to be distributed as a standalone installable (maybe brew install inlang), then using our Ecosystem in other Languages would become much easier.