In containers, can't set DATAVERSE_SITEURL using documented methods

[pdurbin]

For context, I'm working on the following pull request...

• Tutorial for running containers as a demo or for evaluation #10273

... trying to help push our containers from "dev mode" to "demo mode".

A very important setting for a demo is dataverse.siteUrl but I can't set it using a Docker compose.yml using any of the methods documented at https://guides.dataverse.org/en/6.1/installation/config.html#dataverse-siteurl

These don't work:

    environment:
      DATAVERSE_SITEURL: "https://demo.dataverse.org"

    environment:
      JVM_ARGS: -Ddataverse.siteUrl=https://demo.dataverse.org

@poikilotherm explained a workaround that does work:

      _CT_DATAVERSE_SITEURL: "https://demo.dataverse.org"

That is to say, you have to prepend _CT_, probably because it's the name of the profile we use.

This affects other settings as well, such as DATAVERSE_SOLR_HOST.

My understanding of the problem is that we explicitly set the siteUrl here...

https://github.com/IQSS/dataverse/blob/v6.1/src/main/resources/META-INF/microprofile-config.properties#L9

... as %ct.dataverse.siteUrl=http://${dataverse.fqdn}:8080 and we can't override it the way we expect.

For now, for the demo/eval tutorial, I'll simply document the _CT_ workaround, but I'm opening this issue to resolve the underlying problem.

The following PR by @poikilotherm was already merged...

• Clarify how source ordinal applies with an active profile eclipse/microprofile-config#782

... and Payara 6.2023.12 and newer might include a fix. We should test and see.

There's additional discussion in Zulip: https://dataverse.zulipchat.com/#narrow/stream/375812-containers/topic/MPC.20profile.20problem/near/358512660

I'm giving this a size or 3 for:

• build base image with latest Payara
• test if the workaround is no longer needed
• if not needed, talk more with the team about upgrading Payara
• if still needed, report to Payara that the bug hasn't been fixed yet