Use support email in the system email message "closing" text

[PaulBoon]

What this PR does / why we need it:
Uses the support email address (when configured) in the system email 'closing' text, which refers to contacting support.

Which issue(s) this PR closes:

Closes #10287

Special notes for your reviewer:

Suggestions on how to test this:
Force an email sent to you, for instance by requesting to change the password.
When the support email has been configured and is different from the system email it should show that at the end of the email message ('from' is still the system email).
When the support email is not configured the system email should be used instead.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:
Warn sysadmins that if they have set that support-email, that will be used in those emails and if they don't want that they should either change or remove it.

Additional documentation:

[coveralls]

coverage: 20.72% (+0.001%) from 20.719%
when pulling fdb5932 on PaulBoon:UseSupportEmailInClosingText
into e6b2661 on IQSS:develop.

[pdurbin]

This seems fine but can you please add docs and a release note?

[PaulBoon]

@pdurbin would be great if this is moved to QA

[pdurbin]

@PaulBoon well, it's not up to me. 😄

@cmbz and @scolapasta how to do you feel about prioritizing this?

Do note that for Harvard Dataverse (according to recent support tickets), the email closing already ends with a support address...

"You may contact us for support at support@dataverse.harvard.edu.

Thank you,
Harvard Dataverse Support"

... so I suppose this means that we don't have dataverse.mail.support-email configured. Basically, there should be no change for Harvard Dataverse (not that I've tested this PR). But it will help other installations, like DANS.

[pdurbin]

Just a suggestion to change straight quotes to double quotes. (I should write this up in a style guide.)

[Louis-wr]

Hi,
Is there any planed progress on this? @PaulBoon @pdurbin

[pdurbin]

@Louis-wr it's a nice, small change. I'm ok with it being moved forward. I threw a small size on it (3).

@qqmyers this is under "external commitments (Jim)" right now. I'm not sure why.

@cmbz @scolapasta how do you feel about prioritizing this for an upcoming sprint?

[cmbz]

Okay by me, just noting though that there are a large number of items currently in Sprint Ready, so it might take a while if @scolapasta agrees.

[pdurbin]

@PaulBoon I don't have permission to push to your fork. Can you please merge the latest from the "develop" branch into this pull request? It should resolve the error I'm seeing:

dev_dataverse> /opt/payara/scripts/init_2_configure.sh: line 55: POSTBOOT_COMMANDS: unbound variable

Thanks!

[coveralls]

Changes unknown
when pulling 167799f on PaulBoon:UseSupportEmailInClosingText
into ** on IQSS:develop**.

[PaulBoon]

@pdurbin Just had some trouble pulling and pushing, but it should be ok now.

[pdurbin]

@PaulBoon thanks, this seems to work fine. I'm seeing the email I configured (in blue, below)...

... when I put it in my docker compose file:

% git diff docker-compose-dev.yml
diff --git a/docker-compose-dev.yml b/docker-compose-dev.yml
index 402a95c0e1..407b509044 100644
--- a/docker-compose-dev.yml
+++ b/docker-compose-dev.yml
@@ -24,6 +24,7 @@ services:
       DATAVERSE_AUTH_OIDC_CLIENT_SECRET: 94XHrfNRwXsjqTqApRrwWmhDLDHpIYV8
       DATAVERSE_AUTH_OIDC_AUTH_SERVER_URL: http://keycloak.mydomain.com:8090/realms/test
       DATAVERSE_SPI_EXPORTERS_DIRECTORY: "/dv/exporters"
+      DATAVERSE_MAIL_SUPPORT_EMAIL: foo@bar.com
       # These two oai settings are here to get HarvestingServerIT to pass
       dataverse_oai_server_maxidentifiers: "2"
       dataverse_oai_server_maxrecords: "2"

Merging.