Update IntelliJ run configurations and service scripts

[labkey-adam]

Rationale

Need to add --add-opens=java.base/java.io=ALL-UNNAMED flag to JVM startup options for Snowflake

[labkey-tchad]

Do we know how this lists were determined? The IntelliJ run configurations don't match the embedded install scripts; nor do they match what we specify when starting Tomcat with Gradle.
They seem to match standalone Tomcat, but not quite.

[labkey-adam]

Do we know how this lists were determined? The IntelliJ run configurations don't match the embedded install scripts; nor do they match what we specify when starting Tomcat with Gradle. They seem to match standalone Tomcat, but not quite.

I can't tell you the full history here. These have evolved over time as we've discovered issues or added libraries that require specific flags (like the Snowflake JDBC driver). I'm not surprised that Tomcat's standard list and ours are different. Tomcat has a lot of features that LabKey never uses and LabKey has dependencies that Tomcat doesn't. We should be self consistent, though. Maybe we should try reconciling once we drop standalone Tomcat support and the corresponding startup scripts.

[labkey-jeckels]

This change seems fine but I like the followup idea for making them more consistent.

@labkey-stuartm @labkey-willm @labkey-jony heads up as I imagine this would need to propagate to cloud deployments when/if someone attempts to adopt Snowflake. That involves adding a new data source to application.properties, so there would also be other config customizations for an instance to adopt it.

[labkey-adam]

This change seems fine but I like the followup idea for making them more consistent.

@labkey-stuartm @labkey-willm @labkey-jony heads up as I imagine this would need to propagate to cloud deployments when/if someone attempts to adopt Snowflake. That involves adding a new data source to application.properties, so there would also be other config customizations for an instance to adopt it.

@labkey-stuartm @labkey-willm @labkey-jony @labkey-jeckels Snowflake usage will likely be low, and probably non-existent on our cloud deployments for the foreseeable future, but I'd still be in favor of adding this flag everywhere, including all of our startup scripts, service definitions, etc. for consistency. I've added a task to the Snowflake story.

[labkey-stuartm]

This change seems fine but I like the followup idea for making them more consistent.
@labkey-stuartm @labkey-willm @labkey-jony heads up as I imagine this would need to propagate to cloud deployments when/if someone attempts to adopt Snowflake. That involves adding a new data source to application.properties, so there would also be other config customizations for an instance to adopt it.

@labkey-stuartm @labkey-willm @labkey-jony @labkey-jeckels Snowflake usage will likely be low, and probably non-existent on our cloud deployments for the foreseeable future, but I'd still be in favor of adding this flag everywhere, including all of our startup scripts, service definitions, etc. for consistency. I've added a task to the Snowflake story.

Java_Reflection_Ops added with this PR LabKey/install-script#72