Notifications API: remove hard-coded dataset urls from message text

[ekraffmiller]

In the Notifications API, the message text sometimes contains a hard-coded reference to the JSF Dataset page. This needs to be more dynamic so that it can be used by the SPA, or other clients that don't use the JSF frontend.

For example, here are some notifications currently defined in the bundle.properties:

notification.ingestCompleted=Dataset <a href="/dataset.xhtml?persistentId={0}" title="{1}">{1}</a> has one or more tabular files that completed the <a href="{2}/{3}/user/dataset-management.html#tabular-data-files" title="Tabular Data Files - Dataverse User Guide" target="_blank" rel="noopener">tabular ingest process</a> and are available in archival formats.
notification.ingestCompletedWithErrors=Dataset <a href="/dataset.xhtml?persistentId={0}" title="{1}">{1}</a> has one or more tabular files that are available but are not supported for <a href="{2}/{3}/user/dataset-management.html#tabular-data-files" title="Tabular Data Files- Dataverse User Guide" target="_blank" rel="noopener">tabular ingest</a>.

As a temporary solution while both JSF and SPA UIs are deployed, an extra parameter can be defined on the endpoint, a flag that specifies that all links within the messages should be SPA links. By default, the JSF links can be returned.

[qqmyers]

FWIW: For something like this, I think redefining the API to only give the parameters, e.g. the message type, and the {0}, {1}, {2} parameters ("pid":"doi:10.5072/FK2ABCDEF", "title":"My Best Dataset", "guides_url": ...) and having the SPA (and other clients) manage the text, would be better than trying to add flexibility to generate multiple string variants on the back end. (#11644 is ~similar in that we have another API where we're trying to generate the right message for the UI via an API (in this case needing to know the language) - rather than adding a locale parameter, the API could just send 0 as a result and allow the UI to craft the right text.)

[pdurbin]

Sure, let's move text to the SPA but email notifications are sent out by the backend so we can't move them.

I spent an hour or so futzing with code. Here's a draft PR, just for conversation:

• introduce "UI" setting for JSF vs SPA #11665