Change file monitoring for LCLS to support custom config files

[evie-lau]

To support custom config files, after OpenLiberty/liberty-language-server#212 goes in, the IDE client side needs to be changed to monitor the following to send to LCLS:

• all .env and .properties files - language support. Lines to change shown below:

liberty-tools-eclipse/bundles/io.openliberty.tools.eclipse.lsp4e/plugin.xml

Lines 47 to 67 in 2fb4b6b

	<extension
	point="org.eclipse.core.contenttype.contentTypes">
	<content-type
	base-type="org.eclipse.core.runtime.text"
	file-names="bootstrap.properties"
	id="io.openliberty.tools.eclipse.org.liberty.tools.config.bootstrap-properties"
	name="Liberty Server Bootstrap Properties"
	priority="normal">
	</content-type>
	</extension>
	<extension
	point="org.eclipse.core.contenttype.contentTypes">
	<content-type
	base-type="org.eclipse.core.runtime.text"
	file-names="server.env"
	id="io.openliberty.tools.eclipse.org.liberty.tools.config.server-env"
	name="Liberty Server Env Settings"
	priority="normal">
	</content-type>
	</extension>

• liberty-plugin-config.xml - watch file for changes.
  LSP protocol workspace/didChangeWatchedFiles possibly not supported, as per Support for workspace/didChangeWatchedFiles eclipse/lsp4e#807

Not changing it shouldn't break anything, but will not have support for custom config files.

Can model after OpenLiberty/liberty-tools-vscode#286

[scottkurz]

Thx for the details.

Since not changing this shouldn't break anything I'll file this under the 23.0.12 milestone to target for that release.

[evie-lau]

An update: implementing this change also will not break anything - so it can be done anytime.

[cherylking]

Just a quick note that I think you need to change that same file to send all XML files to LCLS, instead of just server.xml. LCLS will then check for the server root element to decide if the file gets support.

[scottkurz]

Seems like we're not going to be able to get updates on the liberty plugin cfg via DidChangeWatchedFiles eclipse/lsp4e#547

[scottkurz]

Closing this since we did the biggest piece in #460.

We still have a smaller effort remaining: #461 to be able to react dynamically to updates to the plugin cfg. For the time being the user will have to do some kind of restart...either of the IDE or dev mode. Would be nice to have doc but if we're going to fix anyway maybe it's not as much of a priority.