Problem:
The Tailwind CSS language server is enabled for any workspace containing
a `.git` folder, a `node_modules` folder, or a `package.json` file, which is
not ideal.
Solution:
Introduce a specific check for the `tailwindcss` package within `package.json`
file using `insert_package_json` method from `util` (this approach is used in
`eslint` config). Since the latest version of Tailwind CSS (v4) no longer
requires `postcss.config.*` and `tailwind.config.*` files, these can no longer
be relied upon as sole criteria for enabling Tailwind CSS LSP.
Problem:
The name `server_configurations` is extremely verbose and irritatingly
formal and dogmatic. This overlong name is a constant nuisance when
reading, writing, and coding.
It's also not even correct: these configurations are just as much
"client" configurations as they are "server" configurations.
Solution:
- Rename to a shorter name.
- Leave placeholder files for any old URLs that link to the old
location.
