[bug] [LSP Server] CJS configuration files in ESM projects cannot be cache busted on the server

[spence-s]

Internally, XO uses cosmiconfig to load configuration files.

In the case a project is ESM and the xo.config.cjs or .xo-config.cjs is used, the configuration file will not be invalidated until the server process is restarted, this means that the server cannot invalidate a cjs config on its own, the client must restart the process in that case.

This problem cannot be solved on the server and will remain a bug for anyone using the server directly:

CJS configuration files in ESM projects do not freshly import
Invalidate cache when using import #49442](nodejs/node#49442)

VSCode extensions users will automatically restart the server process from the client as a work around.

[spence-s]

the extension now restarts on config change